Charlie Marsh 35b982446d Respect pre-release preferences from input files (#5736) ... ## Summary Right now, if you have a `requirements.txt` with a pre-release, but the `requirements.in` does not have a pre-release marker for that dependency we drop the pre-release. (In the selector, we end up returning `AllowPrerelease::IfNecessary`, the default.) I played with a few ways of solving this... The first was to remove that guard altogether. But if we do that, `universal_transitive_disjoint_prerelease_requirement` fails (we use `1.17.0rc1` in both forks, when it should only apply to one of the two). The second was to do that, but also avoid pushing pre-releases as preferences when we solve a fork. But then `universal_disjoint_prereleases` fails, because we return a different pre-release in each fork. Finally, I settled on allowing existing pre-releases in forks if they have no markers on them, i.e., they are "global" preferences. I believe this is true IFF the preference came from an existing lockfile. Closes https://github.com/astral-sh/uv/issues/5729.		2024-08-02 22:01:58 -04:00
..
src	Respect pre-release preferences from input files (#5736)	2024-08-02 22:01:58 -04:00
Cargo.toml	Capture portable path serialization in a struct (#5652)	2024-07-31 16:00:37 +00:00