Changed static type annotations in prereleases setter method in specifier.py #930
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
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.
There are two changes made to the value parameters of the
prereleasessetter methods of theSpecifierandSpecifierSetclass, since both of them are acceptingNonevalues at runtime from the unit tests. The links to the unit tests are as follows where they are accepting None values as arguments to the value parameter even though it is statically annotated asbool.packaging/tests/test_specifiers.py
Line 497 in e5470c1
packaging/tests/test_specifiers.py
Line 746 in e5470c1