➜

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.23:38:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630539496.99.0.209847267339.issue40360@roundup.psfhosted.org>
In-reply-to
Content 
Guido: How come the deprecation didn't happen in 3.10? Were people just not interested?

Well, if nobody deprecates it, it's not deprecated. It is simple as it it :-)

IMO it's ok to only deprecate it in Python 3.11, unless Pablo *really* wants to deprecate lib2to3 before just Python 3.10 final.

I dislike adding new warnings between a beta1 release and the final release :-( In my experience, it *does* break projects which care of warnings.
History
Date User Action Args
2021-09-01 23:38:17vstinnersetrecipients: + vstinner, gvanrossum, gregory.p.smith, carljm, eric.snow, davidhalter, hroncok, corona10, miss-islington, xtreak, BTaskaya, Peter Ludemann
2021-09-01 23:38:16vstinnersetmessageid: <1630539496.99.0.209847267339.issue40360@roundup.psfhosted.org>
2021-09-01 23:38:16vstinnerlinkissue40360 messages
2021-09-01 23:38:16vstinnercreate