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

Fix up reference to environment markers in resolver reference (#6773)

Browse source
This commit is contained in:
Zanie Blue 2024-08-28 17:00:43 -05:00 • committed by GitHub
parent c730530b4e
commit aad00d22e4
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/resolver-internals.md
View file

@ -107,7 +107,7 @@ One difficulty in a forking resolver is that where splits occur is dependent on
are seen, which is in turn dependent on the preferences, e.g., from `uv.lock`. So it is possible for are seen, which is in turn dependent on the preferences, e.g., from `uv.lock`. So it is possible for
the resolver to solve the requirements with specific forks, write this to the lockfile, and when the the resolver to solve the requirements with specific forks, write this to the lockfile, and when the
resolver is invoked again, a different solution is found because the preferences result in different resolver is invoked again, a different solution is found because the preferences result in different
fork points. To avoid this, the `environment-markers` of each fork and each package that diverges fork points. To avoid this, the `resolution-markers` of each fork and each package that diverges
between forks is written to the lockfile. When performing a new resolution, the forks from the between forks is written to the lockfile. When performing a new resolution, the forks from the
lockfile are used to ensure the resolution is stable. When requirements change, new forks may be lockfile are used to ensure the resolution is stable. When requirements change, new forks may be
added to the saved forks. added to the saved forks.