From 282d6911584768c5a2f8ab54eb11f7bb4fe00d44 Mon Sep 17 00:00:00 2001 From: Brett Cannon Date: Tue, 16 Jun 2020 12:47:42 -0700 Subject: [PATCH] Define "backwards incompatibility" --- pep-0387.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/pep-0387.txt b/pep-0387.txt index f21a337fb..69e44bb2b 100644 --- a/pep-0387.txt +++ b/pep-0387.txt @@ -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 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 =============================