mirrors/uv
1
0
Fork 0
mirror of https://github.com/astral-sh/uv.git synced 2025-11-19 11:35:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Fix typo in resolver internal docs (#16232)

Browse source
This commit is contained in:
konsti 2025-10-10 17:46:47 +02:00 • committed by GitHub
parent d5dd43aa18
commit d45acaebc8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/reference/internals/resolver.md
View file

@ -194,7 +194,7 @@ published.
Ignoring an upper bound is a problem for packages such as numpy which use the version-dependent C Ignoring an upper bound is a problem for packages such as numpy which use the version-dependent C
API of CPython. As of writing, each numpy release support 4 Python minor versions, e.g., numpy 2.0.0 API of CPython. As of writing, each numpy release support 4 Python minor versions, e.g., numpy 2.0.0
has wheels for CPython 3.9 through 3.12 and declares `requires-python = ">=3.9"`, while numpy 2.1.0 has wheels for CPython 3.9 through 3.12 and declares `requires-python = ">=3.9"`, while numpy 2.1.0
has wheels for CPython 3.10 through 3.13 and declares `requires-python = ">=3.10"`. The means that has wheels for CPython 3.10 through 3.13 and declares `requires-python = ">=3.10"`. This means that
when uv resolves a `numpy>=2,<3` requirement in a project with `requires-python = ">=3.9"`, it when uv resolves a `numpy>=2,<3` requirement in a project with `requires-python = ">=3.9"`, it
selects numpy 2.0.0 and the lockfile doesn't install on Python 3.13 or newer. To alleviate this, selects numpy 2.0.0 and the lockfile doesn't install on Python 3.13 or newer. To alleviate this,
whenever uv rejects a version that requires a newer Python version, we fork by splitting the whenever uv rejects a version that requires a newer Python version, we fork by splitting the