Forbid prefix version matching on pre-release/post-release segments #563
Conversation
This file contains hidden or 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
|
Just a quick FYI that I have some pathlib PRs I need to get cleared out on the CPython side, but after that I'm planning to swing back over to |
It does not make much sense to have this. Let's forbid it.
brettcannon
approved these changes
Aug 21, 2022
KOLANICH
pushed a commit
to KOLANICH-libs/packaging
that referenced
this pull request
Nov 30, 2022
…ypa#563) It does not make much sense to have this. Let's forbid it. Co-authored-by: Brett Cannon <brett@python.org>
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.
It does not make much sense to have this.
Let's forbid it.
Per https://discuss.python.org/t/pep-440-clarification-on-prefix-version-matching-with-pre-release-post-release-segments/16622/3
closes #425
closes #562