This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author A. Skrobov
Recipients A. Skrobov, benjamin.peterson, berker.peksag, brett.cannon, fdrake, giampaolo.rodola, gregory.p.smith, pablogsal, python-dev, serhiy.storchaka, xcombelle
Date 2019-03-11.20:19:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The major problem with the parser module is that is unsynchronized with the actual parser

The parser module is "sort of" synchronised with the actual parser, in that it uses the same _PyParser_Grammar; this doesn't mean they always behave the same, as this bug shows :-)

(But before #26526, it used to be much worse, with the parser module having a completely independent re-implementation of the parser.)

> As a side note, the problem described in this bug was more or less foreseen. This is in the header of Modules/parsemodule.c:

Just to clarify, the bug is not about the cryptic exception message, it's about the exception firing when it shouldn't.
Date User Action Args
2019-03-11 20:19:42A. Skrobovsetrecipients: + A. Skrobov, fdrake, brett.cannon, gregory.p.smith, giampaolo.rodola, benjamin.peterson, python-dev, berker.peksag, serhiy.storchaka, xcombelle, pablogsal
2019-03-11 20:19:42A. Skrobovsetmessageid: <>
2019-03-11 20:19:42A. Skrobovlinkissue36256 messages
2019-03-11 20:19:42A. Skrobovcreate