➜

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 brett.cannon
Recipients A. Skrobov, benjamin.peterson, berker.peksag, brett.cannon, fdrake, gregory.p.smith, pablogsal, python-dev, serhiy.storchaka, xcombelle
Date 2019-03-12.18:18:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1552414696.88.0.451164568451.issue36256@roundup.psfhosted.org>
In-reply-to
Content 
It's sounding like it might be worth the effort then to make lib2to3's parser not be a "hidden" thing in lib2to3, break it out as a new parser module (I have no stance on name), and then deprecate the old parser module. I think this was discussed at the last language summit when Christian proposed deprecating lib2to3 and everyone said the parser is too useful to lose.
History
Date User Action Args
2019-03-12 18:18:16brett.cannonsetrecipients: + brett.cannon, fdrake, gregory.p.smith, benjamin.peterson, python-dev, berker.peksag, serhiy.storchaka, xcombelle, A. Skrobov, pablogsal
2019-03-12 18:18:16brett.cannonsetmessageid: <1552414696.88.0.451164568451.issue36256@roundup.psfhosted.org>
2019-03-12 18:18:16brett.cannonlinkissue36256 messages
2019-03-12 18:18:16brett.cannoncreate