Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PEP 387: Suggest waiting 5 years before removing a deprecated feature #4156

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

PEP 387: Suggest waiting 5 years before removing a deprecated feature #4156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions peps/pep-0387.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,10 +169,11 @@ several releases:

3. 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.0, 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, for example:
major version (e.g., for a warning in Python 3.10.0, you either wait
until at least Python 3.12 or Python 4.0 to make the change). It is
preferred, though, to wait 5 years before removal (e.g., warn starting in
Python 3.10, removal in 3.15; this happens to coincide with the current
lifetime of a minor release of Python).

- If the expected maintenance overhead and security risk of the
deprecated behavior is small (e.g. an old function is reimplemented
Expand Down
Loading