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

PEP 440: Resolve uses of the default role (#3395)

This commit is contained in:
Adam Turner 2023-09-01 20:28:04 +01:00 committed by GitHub
parent 09e6c75fd8
commit 8a318a5400
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
pep-0440.txt
View File

@ -93,10 +93,10 @@ this scheme but MUST also include the normalizations specified below.
Installation tools MAY warn the user when non-compliant or ambiguous versions Installation tools MAY warn the user when non-compliant or ambiguous versions
are detected. are detected.
See also `Appendix B : Parsing version strings with regular expressions` which See also ``Appendix B : Parsing version strings with regular expressions``
provides a regular expression to check strict conformance with the canonical which provides a regular expression to check strict conformance with the
format, as well as a more permissive regular expression accepting inputs that canonical format, as well as a more permissive regular expression accepting
may require subsequent normalization. inputs that may require subsequent normalization.
Public version identifiers are separated into up to five segments: Public version identifiers are separated into up to five segments:
@ -650,10 +650,10 @@ are permitted and MUST be ordered as shown::
.devN, aN, bN, rcN, <no suffix>, .postN .devN, aN, bN, rcN, <no suffix>, .postN
Note that `c` is considered to be semantically equivalent to `rc` and must be Note that ``c`` is considered to be semantically equivalent to ``rc`` and must
sorted as if it were `rc`. Tools MAY reject the case of having the same ``N`` be sorted as if it were ``rc``. Tools MAY reject the case of having the same
for both a ``c`` and a ``rc`` in the same release segment as ambiguous and ``N`` for both a ``c`` and a ``rc`` in the same release segment as ambiguous
remain in compliance with the PEP. and remain in compliance with the PEP.
Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate Within an alpha (``1.0a1``), beta (``1.0b1``), or release candidate
(``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be (``1.0rc1``, ``1.0c1``), the following suffixes are permitted and MUST be
@ -1296,7 +1296,7 @@ trailing ``\n`` character were found on PyPI.
Various other normalisation rules were also added as described in the Various other normalisation rules were also added as described in the
separate section on version normalisation below. separate section on version normalisation below.
`Appendix A` shows detailed results of an analysis of PyPI distribution ``Appendix A`` shows detailed results of an analysis of PyPI distribution
version information, as collected on 8th August, 2014. This analysis version information, as collected on 8th August, 2014. This analysis
compares the behavior of the explicitly ordered version scheme defined in compares the behavior of the explicitly ordered version scheme defined in
this PEP with the de facto standard defined by the behavior of setuptools. this PEP with the de facto standard defined by the behavior of setuptools.
@ -1599,7 +1599,7 @@ Metadata v2.0 guidelines versus setuptools::
Appendix B : Parsing version strings with regular expressions Appendix B : Parsing version strings with regular expressions
============================================================= =============================================================
As noted earlier in the `Public version identifiers` section, published As noted earlier in the ``Public version identifiers`` section, published
version identifiers SHOULD use the canonical format. This section provides version identifiers SHOULD use the canonical format. This section provides
regular expressions that can be used to test whether a version is already regular expressions that can be used to test whether a version is already
in that form, and if it's not, extract the various components for subsequent in that form, and if it's not, extract the various components for subsequent