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

Use the right term in PEP 426

This commit is contained in:
Nick Coghlan 2013-02-10 00:28:52 +10:00
parent 659b0fe69a
commit 0a825fe2ee
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pep-0426.txt
View File

@ -897,12 +897,12 @@ them to the standard scheme. This means that projects using non-compliant
version identifiers may not be handled consistently across different tools, version identifiers may not be handled consistently across different tools,
even when correctly publishing the earlier metadata versions. even when correctly publishing the earlier metadata versions.
Package developers can help ensure consistent automated handling by Distribution developers can help ensure consistent automated handling by
marking non-compliant versions as "hidden" on the Python Package Index marking non-compliant versions as "hidden" on the Python Package Index
(removing them is generally undesirable, as users may be depending on (removing them is generally undesirable, as users may be depending on
those specific versions being available). those specific versions being available).
Package users may also wish to remove non-compliant versions from any Distribution users may also wish to remove non-compliant versions from any
private package indexes they control. private package indexes they control.
For metadata v1.2 (PEP 345), the version ordering described in this PEP For metadata v1.2 (PEP 345), the version ordering described in this PEP