Message372814
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:40 | christian.heimes | set | recipients:
+ christian.heimes, methane |
2020-07-02 07:20:40 | christian.heimes | set | messageid: <1593674440.09.0.747120917624.issue41165@roundup.psfhosted.org> |
2020-07-02 07:20:40 | christian.heimes | link | issue41165 messages |
2020-07-02 07:20:39 | christian.heimes | create | |
|