[Python-checkins] peps: PEP 426: Update the section on handling old non-compliant versions
nick.coghlan
python-checkins at python.org
Thu Feb 21 15:10:35 CET 2013
http://hg.python.org/peps/rev/22fac210d100
changeset: 4759:22fac210d100
user: Nick Coghlan <ncoghlan at gmail.com>
date: Fri Feb 22 00:10:25 2013 +1000
summary:
PEP 426: Update the section on handling old non-compliant versions
files:
pep-0426.txt | 23 ++++++++++++-----------
1 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/pep-0426.txt b/pep-0426.txt
--- a/pep-0426.txt
+++ b/pep-0426.txt
@@ -897,19 +897,20 @@
acknowledges that the de facto standard for ordering them is
the scheme used by the ``pkg_resources`` component of ``setuptools``.
-Software that automatically processes distribution metadata may either
-treat non-compliant version identifiers as an error, or attempt to normalize
-them to the standard scheme. This means that projects using non-compliant
-version identifiers may not be handled consistently across different tools,
-even when correctly publishing the earlier metadata versions.
+Software that automatically processes distribution metadata should attempt
+to normalize non-compliant version identifiers to the standard scheme, and
+ignore them if normalization fails. As any normalization scheme will be
+implementation specific, this means that projects using non-compliant
+version identifiers may not be handled consistently across different
+tools, even when correctly publishing the earlier metadata versions.
-Distribution developers can help ensure consistent automated handling by
-marking non-compliant versions as "hidden" on the Python Package Index
-(removing them is generally undesirable, as users may be depending on
-those specific versions being available).
+For distributions currently using non-compliant version identifiers, these
+filtering guidelines mean that it should be enough for the project to
+simply switch to the use of compliant version identifiers to ensure
+consistent handling by automated tools.
-Distribution users may also wish to remove non-compliant versions from any
-private package indexes they control.
+Distribution users may wish to explicitly remove non-compliant versions from
+any private package indexes they control.
For metadata v1.2 (PEP 345), the version ordering described in this PEP
should be used in preference to the one defined in PEP 386.
--
Repository URL: http://hg.python.org/peps
More information about the Python-checkins
mailing list