Message363285
> Can I ask what sort of backwards-compatibility guarantees Python provides for these cases?
A deprecation warning for two releases (i.e. two years). Then it can be removed. So if people want to move forward with removing this then a DeprecationWarning would need to be raised in all places where _closed is set with a message stating the functionality is deprecated in 3.9 and slated for removal in 3.11 (along with appropriate doc updates, both for the module and What's New). |
|
Date |
User |
Action |
Args |
2020-03-03 18:08:24 | brett.cannon | set | recipients:
+ brett.cannon, pitrou, Antony.Lee, barneygale |
2020-03-03 18:08:24 | brett.cannon | set | messageid: <1583258904.52.0.825119549098.issue39682@roundup.psfhosted.org> |
2020-03-03 18:08:24 | brett.cannon | link | issue39682 messages |
2020-03-03 18:08:24 | brett.cannon | create | |
|