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.
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
*args regression #68979
Comments
The following code is allowed by the grammar of Python 3.4, but not Python 3.5:
where unary
The cause of the regression that the 3.4 grammar for Thanks to zware on IRC for actually testing this for me, since I don't have a runnable python3.5, just docs. |
Related: bug 24176 fixed this for the |
New changeset 3c170f68407f by Zachary Ware in branch '3.4': |
Test committed on 3.4; I'm not comfortable enough with the grammar to actually fix the issue (the obvious change of |
The attached patch should fix that. Please review. |
Also consider: *() or (), *() or () Note that the second-or-later argument is a separate part of the grammar so that's why I wrote it twice. Actually, I think |
I'm not so concerned with supporting [*[] or []] stuff, but rather fixing the immediate regression in 3.5.0. I'd keep the patch size to the minimum. |
New changeset e4cb64628673 by Yury Selivanov in branch '3.5': New changeset 4c89dd5199e5 by Yury Selivanov in branch 'default': |
New changeset 40c391d12741 by Yury Selivanov in branch '3.5': New changeset a572137b4f05 by Yury Selivanov in branch 'default': |
New changeset 20e0906a808e by Terry Jan Reedy in branch '3.5': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: