From e36583e22497a41b998967f6482ca6e784df5a22 Mon Sep 17 00:00:00 2001 From: Nick Coghlan Date: Thu, 19 Mar 2015 13:10:44 +1000 Subject: [PATCH] PEP 440 is no longer provisional --- pep-0440.txt | 24 +++--------------------- 1 file changed, 3 insertions(+), 21 deletions(-) diff --git a/pep-0440.txt b/pep-0440.txt index e91918273..6757b8400 100644 --- a/pep-0440.txt +++ b/pep-0440.txt @@ -27,23 +27,6 @@ This document addresses several limitations of the previous attempt at a 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 @@ to a ``file://`` url, it would end up as ``file://machine/volume/file``. For 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