potiuk commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2040039543
Good input. Thanks @notatallshaw :) > In general the behavior of uv's resolution algorithm (powered by pugrub-rs) has a tendency to want to exchaust all possible versions of a particular package more likely than pip's resolution algorithm (powered by resolvelib), though pip does sometimes produce the same behavior under certain circumstances. I suggested in my issue that `uv` could (at least initially) limit a number of versions considered. For example in certain cases - like installing most recent packages - limit all transient dependencies to say max. 2 years old or 10 versions. Even if that would fail, you can repeat it with relaxed limits. This kind of heuristics could save a lot of hassle. > For this issue of a bad specifier, pip currently supports a very wide range of specifiers and versions due to using legacy specifier and version from an older version of packaging, however pip is going to drop legacy specifiers and versions likely in the next version of pip. So pip is going to become less lenient than uv, and therefore is going to skip over bad specifiers and versions, uv should do the same (and in fact I think uv should eventually drop supporting any kind of bad versions or specifiers). Agree. `uv` has the big advntage for now that it does not `have` to support all those legacy cases - far less number of people will complain if something won't work :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
