Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for PEP 646 syntax #3014

Closed
JelleZijlstra opened this issue Apr 14, 2022 · 0 comments · Fixed by #3071
Closed

Add support for PEP 646 syntax #3014

JelleZijlstra opened this issue Apr 14, 2022 · 0 comments · Fixed by #3071
Labels
C: parser How we parse code. Or fail to parse it. S: accepted The changes in this design / enhancement issue have been accepted and can be implemented T: enhancement New feature or request

Comments

@JelleZijlstra
Copy link
Collaborator

PEP 646 ads two new pieces of syntax in 3.11 (https://peps.python.org/pep-0646/#grammar-changes):

  • x[a, *b]
  • def f(*args: *T): pass

We should support both and normalize the syntax to have no space after the * (also cc @isidentical).
@JelleZijlstra JelleZijlstra added T: enhancement New feature or request C: parser How we parse code. Or fail to parse it. labels Apr 14, 2022
@ichard26 ichard26 added the S: accepted The changes in this design / enhancement issue have been accepted and can be implemented label Apr 14, 2022
@isidentical isidentical mentioned this issue May 12, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: parser How we parse code. Or fail to parse it. S: accepted The changes in this design / enhancement issue have been accepted and can be implemented T: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement support for PEP 646 isidentical/black
2 participants
@JelleZijlstra @ichard26