Hi there, I noticed some deprecation activity this week. Nice! I'd just like to remind everyone that we have a policy for that described in PEP 387 <https://www.python.org/dev/peps/pep-0387/> It's a very short PEP so I recommend you read it in its entirety. The important piece I want to highlight is that we cannot deprecate a feature in one release and remove it in the next one. We need at least two releases with the warning.
Relevant quotes: > Python's yearly release process (PEP 602 > <https://www.python.org/dev/peps/pep-0602>) means that the deprecation period > must last at least two years. and: > Wait for the warning to appear in at least two minor Python versions of the > same major version, or one minor version in an older major version (e.g. for > a warning in Python 3.10, you either wait until at least Python 3.12 or > Python 4.0 to make the change). It's fine to wait more than two releases. Since this PEP is easy to miss, I linked it to the docs of DeprecationWarning in GH-28123 <https://github.com/python/cpython/pull/28123>. Cheers, Ł
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/WZQIL3GLGO7NYC4XHBVFBHUNUJV6NWLE/ Code of Conduct: https://www.python.org/psf/codeofconduct/
