Charlie Marsh b588054dfb Always use release-only comparisons for requires-python (#4794) ... ## Summary There are a few ideas at play here: 1. pip always strips versions to the release when evaluating against a `Requires-Python`, so we now do the same. That means, e.g., using `3.13.0b0` will be accepted by a project with `Requires-Python: >= 3.13`, which does _not_ adhere to PEP 440 semantics but is somewhat intuitive. 2. Because we know we'll only be evaluating against release-only versions, we can use different semantics in PubGrub that let us collapse ranges. For example, `python_version >= '3.10' or python_version < '3.10'` can be collapsed to the truthy marker. Closes https://github.com/astral-sh/uv/issues/4714. Closes https://github.com/astral-sh/uv/issues/4272. Closes https://github.com/astral-sh/uv/issues/4719.		2024-07-04 20:06:52 +00:00
..
src	Always use release-only comparisons for requires-python (#4794)	2024-07-04 20:06:52 +00:00
Cargo.toml	Change "toolchain" to "python" (#4735)	2024-07-03 07:44:29 -05:00