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 lukasz.langa
Recipients benjamin.peterson, gregory.p.smith, gvanrossum, lukasz.langa, serhiy.storchaka
Date 2018-04-23.23:28:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1524526110.33.0.682650639539.issue33337@psf.upfronthosting.co.za>
In-reply-to
Content
> But lib2to3 is proof that the stdlib is just as much subject to stalling.

The issue here is internal visibility. "lib2to3" is a library that supports "2to3" which is rather neglected internally since we started promoting `six` as a better migration strategy to Python 3.

Most core devs don't even *know* new syntax is supposed to be added to lib2to3.  Case in point: somehow Lib/tokenize.py was updated just in time for f-strings to be released but not Lib/lib2to3/pgen2/tokenize.py.

By unifying the tokenizers and moving the CST out of lib2to3's guts (and documenting it as a supported feature!), I'm pretty sure we can eliminate the danger of forgetting to update it in the future.
History
Date User Action Args
2018-04-23 23:28:30lukasz.langasetrecipients: + lukasz.langa, gvanrossum, gregory.p.smith, benjamin.peterson, serhiy.storchaka
2018-04-23 23:28:30lukasz.langasetmessageid: <1524526110.33.0.682650639539.issue33337@psf.upfronthosting.co.za>
2018-04-23 23:28:30lukasz.langalinkissue33337 messages
2018-04-23 23:28:30lukasz.langacreate