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 BTaskaya, Peter Ludemann, carljm, corona10, davidhalter, eric.snow, gregory.p.smith, gvanrossum, hroncok, lukasz.langa, miss-islington, vstinner, xtreak
Date 2021-09-02.16:25:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The "pending" deprecation status of lib2to3 in 3.9 and 3.10 is no worse than a vanilla deprecation in terms of visibility. It will appear just the same when run with pytest or `-X dev`.

However, upgrading the deprecation between 3.10.0rc1 and 3.10.0rc2 really was too late. So we'll have it deprecated fully in 3.11 and removed in 3.13. One more year doesn't hurt us much but might be helpful for library maintainers to have more time to move off of the included lib2to3.

Invoking `2to3` also generates the warning so I guess this can be closed:

$ ./python.exe Tools/scripts/2to3
/private/tmp/cpy2/Tools/scripts/2to3:3: DeprecationWarning: lib2to3 package is deprecated and may not be able to parse Python 3.10+
  from lib2to3.main import main
At least one file or directory argument required.
Use --help to show usage.

Thanks for the patches, Gregory, Carl, and Victor! ✨ 🍰 ✨  

Now we just have to remember to actually remove the damn thing in 3.13 😂
Date User Action Args
2021-09-02 16:25:23lukasz.langasetrecipients: + lukasz.langa, gvanrossum, gregory.p.smith, vstinner, carljm, eric.snow, davidhalter, hroncok, corona10, miss-islington, xtreak, BTaskaya, Peter Ludemann
2021-09-02 16:25:23lukasz.langasetmessageid: <>
2021-09-02 16:25:23lukasz.langalinkissue40360 messages
2021-09-02 16:25:23lukasz.langacreate