[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Change by Lysandros Nikolaou : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Lysandros Nikolaou added the comment: New changeset c4b58cea4771afc0ddfdb857b0fb5115b9f4bc9f by Lysandros Nikolaou in branch '3.9': [3.9] bpo-41659: Disallow curly brace directly after primary (GH-22996) (#23006)

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Change by Lysandros Nikolaou : -- pull_requests: +21921 pull_request: https://github.com/python/cpython/pull/23006 ___ Python tracker ___

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Lysandros Nikolaou added the comment: New changeset 15acc4eaba8519d7d5f2acaffde65446b44dcf79 by Lysandros Nikolaou in branch 'master': bpo-41659: Disallow curly brace directly after primary (GH-22996) https://github.com/python/cpython/commit/15acc4eaba8519d7d5f2acaffde65446b44dcf79

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Change by Lysandros Nikolaou : -- pull_requests: +21910 pull_request: https://github.com/python/cpython/pull/22996 ___ Python tracker ___

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Change by Lysandros Nikolaou : -- pull_requests: -21195 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Change by Lysandros Nikolaou : -- keywords: +patch pull_requests: +21195 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/22111 ___ Python tracker

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Terry J. Reedy added the comment: Minimal example >>> a{ # or >>> a { In 3.8, this is immediately flagged as a SyntaxError. In 3.9 and master, a continuation prompt is issued. This strikes me as a parsing buglet that should preferably be fixed, as it implies that something valid *could*

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Lysandros Nikolaou added the comment: I had a look at this. I have been testing with the input a{x}, which faces the same problem. It's actually because of an invalid_* rule. The call stack looks like this: ... invalid_comprehension_rule(Parser * p)

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Change by Chrome : -- versions: +Python 3.5, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

Change by Chrome : -- versions: -Python 3.5, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list

[issue41659] PEG discrepancy on 'if {x} {a}: pass'

New submission from Guido van Rossum : I just noticed a subtle discrepancy between the old parser and the PEG parser. Consider this syntax error: ``` if x {a}: pass ``` The old parser places the caret at the '{': ``` $ python3.8 -c 'if x { a } : pass' File "", line 1 if x { a } : pass