Brett Cannon <br...@python.org> added the comment:
> 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). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue39682> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
