Author carljm
Recipients BTaskaya, carljm, eric.snow, gregory.p.smith, gvanrossum
Date 2020-04-22.21:15:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1587590102.69.0.453863524042.issue40360@roundup.psfhosted.org>
In-reply-to
Content
I opened a PR. It deprecates the lib2to3 library to discourage future use of it for Python3, but not the 2to3 tool. This of course means that the lib2to3 module will in practice stick around in the stdlib as long as 2to3 is still bundled with Python.

It seems like the idea in this issue is to deprecate and remove both. I'm not sure what we typically do to deprecate a command-line utility bundled with Python. Given warnings are silent by default, the deprecation warning for lib2to3 won't be visible to users of 2to3. Should I add something to its `--help` output? Or something more aggressive; an unconditionally-printed warning?
History
Date User Action Args
2020-04-22 21:15:02carljmsetrecipients: + carljm, gvanrossum, gregory.p.smith, eric.snow, BTaskaya
2020-04-22 21:15:02carljmsetmessageid: <1587590102.69.0.453863524042.issue40360@roundup.psfhosted.org>
2020-04-22 21:15:02carljmlinkissue40360 messages
2020-04-22 21:15:01carljmcreate