Add Exclusive prerelease specifier scenarios #172
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My first attempt at a PR, let's see how it goes.
This adds two extra scenarios to prerelease specifiers, uv already correctly follows the
>exclusive ordered test: astral-sh/uv#2646, but packaging (and therefore pip) does not: pypa/packaging#788I do not know whether uv implies prerelease from
!=or not, and I'm not explicitly getting it from the the spec but rather following this comment by the spec author pypa/packaging#776 (comment), we can wait and see if the explicit test on that check is accepted by packaging in my PR pypa/packaging#794.