PEP 653: Change semantics to be closer to PEP 634, while keeping the important features of PEP 653. #1868
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
…important features of PEP 653.
markshannon
force-pushed
the
pep-653-closer-to-634
branch
from
49fa795 to
c45b57c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
MATCH_CLASStoMATCH_POSITIONAL.__attributes__and use__match_args__instead.MATCH_DEFAULT,__match_args__acts a map from positions to names.MATCH_POSITIONAL,__match_args__acts a map from names to positions.MATCH_DEFAULTwhen match class patterns to those of PEP 634.