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

Define "backwards incompatibility"

This commit is contained in:
Brett Cannon 2020-06-16 12:47:42 -07:00 committed by GitHub
parent 94a7f4c2cd
commit 282d691158
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
pep-0387.txt
View File

@ -27,6 +27,13 @@ millions of applications and libraries. This is fantastic. However, it
means the development team must be very careful not to break this means the development team must be very careful not to break this
existing 3rd party code with new releases. existing 3rd party code with new releases.
This PEP takes the perspective that "backwards incompatibility" means
preexisting code ceases to comparatively function after a change. It is
acknowledged that this is not a concrete definition, but the expectation
is people in general understand what is meant by
"backwards incompatibility", and if they are unsure they may ask the
Python development team and/or steering council for guidance.
Backwards Compatibility Rules Backwards Compatibility Rules
============================= =============================