mirror of
https://github.com/astral-sh/uv.git
synced 2025-11-01 12:24:15 +00:00
Use "pre-release" in prose and Prerelease in code (#5697)
## Summary Closes https://github.com/astral-sh/uv/issues/5630.
This commit is contained in:
parent
6797caccdb
commit
499c368f1e
26 changed files with 278 additions and 277 deletions
|
|
@ -24,16 +24,16 @@ PEP 440 has a lot of unintuitive features, including:
|
|||
|
||||
* An epoch that you can prefix the version which, e.g. `1!1.2.3`. Lower epoch always means lower
|
||||
version (`1.0 <=2!0.1`)
|
||||
* post versions, which can be attached to both stable releases and prereleases
|
||||
* dev versions, which can be attached to sbpth table releases and prereleases. When attached to a
|
||||
prerelease the dev version is ordered just below the normal prerelease, however when attached
|
||||
to a stable version, the dev version is sorted before a prereleases
|
||||
* prerelease handling is a mess: "Pre-releases of any kind, including developmental releases,
|
||||
* post versions, which can be attached to both stable releases and pre-releases
|
||||
* dev versions, which can be attached to both table releases and pre-releases. When attached to a
|
||||
pre-release the dev version is ordered just below the normal pre-release, however when attached
|
||||
to a stable version, the dev version is sorted before a pre-releases
|
||||
* pre-release handling is a mess: "Pre-releases of any kind, including developmental releases,
|
||||
are implicitly excluded from all version specifiers, unless they are already present on the
|
||||
system, explicitly requested by the user, or if the only available version that satisfies
|
||||
the version specifier is a pre-release.". This means that we can't say whether a specifier
|
||||
matches without also looking at the environment
|
||||
* prelease vs. prerelease incl. dev is fuzzy
|
||||
* pre-release vs. pre-release incl. dev is fuzzy
|
||||
* local versions on top of all the others, which are added with a + and have implicitly typed
|
||||
string and number segments
|
||||
* no semver-caret (`^`), but a pseudo-semver tilde (`~=`)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue