feat: allow pep440 version specifiers in requires-python #123
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
gaborbernat
requested changes
Aug 27, 2023
gaborbernat
approved these changes
Aug 27, 2023
|
Sorry! Forgot to fix the tests. I’ll update them later. |
MindTooth
force-pushed
the
feat/allow_python_requires_range
branch
from
fbf6db7
to
ff3704b
Compare
MindTooth
force-pushed
the
feat/allow_python_requires_range
branch
from
ff3704b
to
1bc4b45
Compare
gaborbernat
approved these changes
Aug 27, 2023
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.
Add support for using PEP440 version specifiers in
requires-python. This allows the user to specify multiple bounds, e.g.<=3.11,!=3.9,>=3.8.Ref. #106, also removesOnlylines.Big thanks to @tomrtk for helping out.
Fixes #99.