➜

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 vstinner
Recipients BTaskaya, Peter Ludemann, carljm, corona10, davidhalter, eric.snow, gregory.p.smith, gvanrossum, hroncok, miss-islington, vstinner, xtreak
Date 2021-09-01.22:23:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630535006.86.0.908531210815.issue40360@roundup.psfhosted.org>
In-reply-to
Content 
I created PR 28116 to deprecate the lib2to3 package: replace PendingDeprecationWarning to DeprecationWarning.

In 2021, I don't think that we should keep the 2to3 tool in the stdlib. Python 2 reached end of line 1 year ago.

For the lib2to3 *parser*, IMO it would be better to maintain it outside the stdlib, and collaborate with other existing forks, like the parser used by Black.

The change is only about *deprecating* lib2to3, not *remove* it. For the removal, we should check if major projects which used it moved to something else.

It's kind of a shame that Python stdlib (lib2to3) cannot parse valid Python 3.10 code :-( IMO it's better to deprecate (and then remove) lib2to3.
History
Date User Action Args
2021-09-01 22:23:26vstinnersetrecipients: + vstinner, gvanrossum, gregory.p.smith, carljm, eric.snow, davidhalter, hroncok, corona10, miss-islington, xtreak, BTaskaya, Peter Ludemann
2021-09-01 22:23:26vstinnersetmessageid: <1630535006.86.0.908531210815.issue40360@roundup.psfhosted.org>
2021-09-01 22:23:26vstinnerlinkissue40360 messages
2021-09-01 22:23:26vstinnercreate