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 christian.heimes
Recipients christian.heimes, methane
Date 2020-07-02.07:20:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm all in favor to remove deprecated things, but please set a tangible deadline first. A lot of these functions have been deprecated for like a decade. Users tend to forget about deprecations or assume that removal was never going to happen. For example the removal of xml.etree.cElementTree broke a bunch of stuff although it had been deprecated since 3.0.

At a bare minimum you should list removed features in the 3.9 changelog and porting guide as "will be removed in 3.10". I would even argue to add deprecation warnings to the code in 3.9 (with permission from the RM). If the RM is against deprecation warnings, then it might be good idea to postpone removal to 3.11.
Date User Action Args
2020-07-02 07:20:40christian.heimessetrecipients: + christian.heimes, methane
2020-07-02 07:20:40christian.heimessetmessageid: <>
2020-07-02 07:20:40christian.heimeslinkissue41165 messages
2020-07-02 07:20:39christian.heimescreate