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 Peter Ludemann
Recipients BTaskaya, Peter Ludemann, benjamin.peterson, fireattack, georg.brandl, gregory.p.smith, lisroach, lukasz.langa, miss-islington, pablogsal, thatch
Date 2020-12-06.20:50:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Every piece of code that uses either lib2to3 or a parser derived from it (including parso and LibCST) will eventually not be able to upgrade the parser because PEG can handle grammars that LL(k) can't. That's why I proposed adding some functionality to ast.parse, to make the whitespace and token information easily available - this seems to be what @BTaskaya says is "easy" (maybe they mean it's easy using LibCST? It seems to be fiddly using ast.parse). The alternative is that all these projects (black, LibCST, yapf, etc.) will have to roll their own solutions, which doesn't seem a very productive use of people's time and makes version upgrades slow.

If people are interested in using ast.parse extensions as a replacement for lib2to3, I suggest discussing at
Date User Action Args
2020-12-06 20:50:10Peter Ludemannsetrecipients: + Peter Ludemann, georg.brandl, gregory.p.smith, benjamin.peterson, thatch, lukasz.langa, fireattack, lisroach, pablogsal, miss-islington, BTaskaya
2020-12-06 20:50:10Peter Ludemannsetmessageid: <>
2020-12-06 20:50:10Peter Ludemannlinkissue36541 messages
2020-12-06 20:50:10Peter Ludemanncreate