> The current backwards compatibility policy (PEP 387) sets a *minimum* > timeline for deprecations and removals -- "deprecation period must last > at least two years."
About the PEP 387 process and the 3 examples. On Fri, Nov 12, 2021 at 11:58 AM Petr Viktorin <encu...@gmail.com> wrote: > AttributeError: module 'configparser' has no attribute > 'SafeConfigParser'. Did you mean: 'RawConfigParser'? > (bpo-45173) SafeConfigParser was not even documented, was deprecated since Python 3.2, and emitted a DeprecationWarning. > ImportError: cannot import name 'formatargspec' from 'inspect' > (bpo-45320) It was deprecated in the doc since Python 3.5, and emitted a DeprecationWarning. > AttributeError: '[...]Tests' object has no attribute 'failUnless' > (bpo-45162) Deprecated in the doc since Python 3.1. It emitted a DeprecationWarning. > But it seems like it's not treated as a minimum > (...) > Note that I am criticizing the *process* On these examples, the functions were deprecated for way longer than a minimum of 2 Python versions, no? Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/L5K4H5O3ZW5DIA6K5XKOAOL4GHMQL532/ Code of Conduct: http://python.org/psf/codeofconduct/
