[Python-checkins] peps: PEP 440 is no longer provisional
nick.coghlan
python-checkins at python.org
Thu Mar 19 04:10:51 CET 2015
https://hg.python.org/peps/rev/8d7b218a99a8
changeset: 5732:8d7b218a99a8
user: Nick Coghlan <ncoghlan at gmail.com>
date: Thu Mar 19 13:10:44 2015 +1000
summary:
PEP 440 is no longer provisional
files:
pep-0440.txt | 24 +++---------------------
1 files changed, 3 insertions(+), 21 deletions(-)
diff --git a/pep-0440.txt b/pep-0440.txt
--- a/pep-0440.txt
+++ b/pep-0440.txt
@@ -27,23 +27,6 @@
standardized approach to versioning, as described in PEP 345 and PEP 386.
-Provisional status of this specification
-========================================
-
-The version representation and comparison scheme described in this PEP is
-currently accepted on a provisional basis [9]_, as described in PEP 411.
-
-This status is based on feedback received on the initial releases of pip 6.0,
-and setuptools 8.0, which revealed some issues in the specification that
-had not been identified prior to acceptance. These issues will be addressed
-within PEP 440 itself, rather than introducing an entirely new PEP to cover
-relatively minor changes to a standard that has only just begun to be adopted.
-
-A future update proposal for PEP 1 will aim to make this Provisional phase
-for the initial release of the reference implementations a formal part of
-the PEP process that can be accurately tracked in the PEP metadata.
-
-
Definitions
===========
@@ -1177,16 +1160,15 @@
more information on ``file://`` URLs on Windows see MSDN [4]_.
-
Updating the versioning specification
=====================================
The versioning specification may be updated with clarifications without
requiring a new PEP or a change to the metadata version.
-Once the Provisional caveat is removed from the specification, any further
-changes to the version comparison semantics will require an updated
-versioning scheme defined in a new PEP.
+Any technical changes that impact the version identification and comparison
+syntax and semantics would require an updated versioning scheme to be
+defined in a new PEP.
Summary of differences from pkg_resources.parse_version
--
Repository URL: https://hg.python.org/peps
More information about the Python-checkins
mailing list