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: Make examples clearer (#2898) 

The PEP 440 version matching examples are confusing to read and the `1.1a1` in `== 1.1.*` is dependent on whether the user requested pre-releases or not, which I've clarified (https://github.com/pypa/packaging/issues/617)
This commit is contained in:
konsti 2023-09-22 23:23:38 +02:00 committed by GitHub
parent d226c15c82
commit a703204b82
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
peps/pep-0440.rst
View File

@ -919,7 +919,7 @@ following clauses would match or not as shown::
== 1.1 # Not equal, so 1.1a1 does not match clause
== 1.1a1 # Equal, so 1.1a1 matches clause
== 1.1.* # Same prefix, so 1.1a1 matches clause
== 1.1.* # Same prefix, so 1.1a1 matches clause if pre-releases are requested
An exact match is also considered a prefix match (this interpretation is
implied by the usual zero padding rules for the release segment of version