[issue46725] Unpacking without parentheses is allowed since 3.9

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue46725] Unpacking without parentheses is allowed since 3.9

miss-islington added the comment: New changeset 7fb94fd7a88f14096a5094d8a979a3912672 by Pablo Galindo Salgado in branch 'main': bpo-46725: Document starred expressions in for statements (GH-31481) https://github.com/python/cpython/commit/7fb94fd7a88f14096a5094d8a979a3912672

[issue46725] Unpacking without parentheses is allowed since 3.9

Pablo Galindo Salgado added the comment: What happened is that the new grammar using the PEG parser used the equivalent of starred_testlist instead of testlist for the iterable list of for statements. The only extra thing allowed is starred elements, that are interpreted as if you are buildi

[issue46725] Unpacking without parentheses is allowed since 3.9

Serhiy Storchaka added the comment: What exactly was happened? What rule was changed? Can it cause other changes which allow ambiguous code or change semantic? -- nosy: +serhiy.storchaka ___ Python tracker

[issue46725] Unpacking without parentheses is allowed since 3.9

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +29612 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31481 ___ Python tracker __

[issue46725] Unpacking without parentheses is allowed since 3.9

Guido van Rossum added the comment: Adding jwilk back (a bpo interaction with browser form caching makes this happen frequently). -- nosy: +jwilk ___ Python tracker ___ _

[issue46725] Unpacking without parentheses is allowed since 3.9

Terry J. Reedy added the comment: Allowing no parentheses is also consistent with the following: for x in 1,2,3: print(x) -- nosy: +terry.reedy -jwilk ___ Python tracker ___

[issue46725] Unpacking without parentheses is allowed since 3.9

Change by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue46725] Unpacking without parentheses is allowed since 3.9

Pablo Galindo Salgado added the comment: Will prepare a PR -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46725] Unpacking without parentheses is allowed since 3.9

Guido van Rossum added the comment: Let's just document it for 3.11. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue46725] Unpacking without parentheses is allowed since 3.9

Erlend E. Aasland added the comment: +1 (what Jelle said) -- nosy: +erlendaasland ___ Python tracker ___ ___ Python-bugs-list maili

[issue46725] Unpacking without parentheses is allowed since 3.9

Jelle Zijlstra added the comment: I'd lean towards keeping this syntax: - It's already been out for two releases, so there's user code out there relying on it. (In fact we found out about this because somebody complained that Black's parser couldn't handle this code.) - The syntax isn't obvio

[issue46725] Unpacking without parentheses is allowed since 3.9

Batuhan Taskaya added the comment: Since this was already allowed in 3.9 and 3.10 stable relases, and since it is consistent with the RHS of an assignment (something = *a, *b); I'd lean towards keeping it (and maybe fixing the old parser's grammar to reflect that) and documenting this.

[issue46725] Unpacking without parentheses is allowed since 3.9

New submission from Pablo Galindo Salgado : Seems that this is allowed since the PEG parser rewrite: for x in *a, *b: print(x) but I cannot find anywhere were we discussed this. I am not sure if we should keep it or treat it as a bug and fix it. -- components: Parser messages: 41