iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 387: clarify how long a warning must be emitted before a change can be made

This commit is contained in:
Brett Cannon 2021-04-16 15:21:47 -07:00 committed by GitHub
parent 84d76bc1cf
commit 307b9cdf88
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
pep-0387.txt
View File

@ -131,8 +131,11 @@ several releases:
incompatibility is expected to become the default and a link to an
issue that users can post feedback to.
3. Wait for the warning to appear in at least two major Python
versions. It's fine to wait more than two 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, 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.
4. See if there's any feedback. Users not involved in the original
discussions may comment now after seeing the warning. Perhaps