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 davidhalter
Recipients BTaskaya, Peter Ludemann, carljm, corona10, davidhalter, eric.snow, gregory.p.smith, gvanrossum, hroncok
Date 2020-07-10.07:17:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm the maintainer of parso. Feel free to addd me to the Nosy List if we have these discussions in the future.

Parso is indeed a lib2to3 fork with error recovery, round tripping and incremental parsing as its features. Most pgen2 code has been rewritten since for various reasons, but it's essentially still LL(1). We're currently trying to think how to proceed with Non-LL(1). For very simple cases a few hacks could suffice, but for larger stuff we will probably need to implement some form of PEG parsing.

I'm mostly worried about incremental parsing breaking if we replace the PEG parser, not about writing the PEG parser. But I guess we'll find a way, because I don't want to abandon Jedi (which depends on parso).
Date User Action Args
2020-07-10 07:17:22davidhaltersetrecipients: + davidhalter, gvanrossum, gregory.p.smith, carljm, eric.snow, hroncok, corona10, BTaskaya, Peter Ludemann
2020-07-10 07:17:22davidhaltersetmessageid: <>
2020-07-10 07:17:22davidhalterlinkissue40360 messages
2020-07-10 07:17:22davidhaltercreate