uv 0.5.0 #197037
Merged
uv 0.5.0 #197037
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
rust
daeho-ro
approved these changes
Nov 8, 2024
|
🤖 An automated task has requested bottles to be published to this PR. |
github-actions
bot
added
the
CI-published-bottle-commits
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.release notes
Use base executable to set virtualenv Python path (#8481)
Previously, uv canonicalized the path to the Python executable when setting the Python path in created virtual environments. This behavior had several undesirable effects: it would bypass stabilized version directories (as constructed by Homebrew) and it was not consistent with the Python standard library's behavior. Now, uv uses the
sys._base_executablepath.Use XDG (i.e.
~/.local/bin) instead of the Cargo home directory in the installer (#8420)Previously, uv's installer used
$CARGO_HOMEor~/.cargo/binfor its target install directory. It's been a longstanding complaint that uv uses this directory, as there's no relationship to Cargo. Now, uv will be installed into$XDG_BIN_HOME,$XDG_DATA_HOME/../bin, or~/.local/bin(in that order). Note that$UV_INSTALL_DIRcan always be used to override the target directory.Discover and respect
.python-versionfiles in parent directories (#6370)Previously, uv only read
.python-versionfiles from the working directory. Now, uv will check parent directories for.python-versionfiles; however uv will not search for.python-versionfiles beyond project boundaries. The new behavior is better aligned with that ofpyenvand Rye.Error when disallowed settings are defined in
uv.toml(#8550)Some settings can only be defined in the
pyproject.toml. Previously, uv would ignore these settings when present in theuv.toml. Now, uv will error to avoid confusion about why the settings are not respeced.Implement PEP 440-compliant local version semantics (#8797)
Previously, uv's implementation of local versions (e.g.
2.0+cpu) was not compliant with the specification due to the technical complexity of implementing the local version semantics in the PubGrub algorithm. Thanks to the work of @ericmarkmartin, uv now has a spec-compliant implementation. Namely, uv will now allow a request fortorch==2.1.0to install[email protected]+cpuregardless of whether[email protected](without a local tag) actually exists.Treat the base Conda environment as a system environment (#7691)
Previously, uv would not distinguish between the base and other Conda environments. Now, uv uses
CONDA_DEFAULT_ENVand the namesbaseanddefaultto determine if an environment active viaCONDA_PREFIXis the base environment. If the base environment is active, the--systemflag must be used to mutate it.Do not allow pre-releases when the
!=operator is used (#7974)Previously, uv would use the presence of a pre-release specifier in a version specifier as an opt-in to allow pre-release versions during resolution. The new behavior does not allow pre-releases when an inequals operator is used, e.g.,
!= 2.0a1.Prefer
USERPROFILEoverFOLDERID_Profilewhen selecting a home directory on Windows (#8048)This change is a side-effect of switching from the
directoriescrate toetceterafor determining canonical system paths. IfUSERPROFILEis not set, the behavior will be unchanged.Improve interactions between color environment variables and CLI options (#8215)
Previously, uv would respect the
FORCE_COLORandNO_COLORenvironment variables over the--colorflag. Now, when the--colorflag is explicitly provided, uv will respect it over the environment variables.Make
allow-insecure-hosta global option (#8476)Previously, this option was only available in some parts of uv. Now,
--allow-insecure-hostcan be provided to any command. For consistency, theallow-insecure-hostsetting has been removed from the[tool.uv.pip]configuration in favor of[tool.uv].Only write
.python-versionfiles duringuv initfor workspace members if the version differs (#8897)Previously, uv would create a
.python-versionfile for workspace members duringuv init. Now, uv will only do so if the version differs from the.python-versionfile in the workspace root since uv will respect.python-versionfiles in parent directories.Enhancements
uv tree --outdated(#8893)pip list --outdated(#8872);on URL and path requirements (#8835)uv cache clean(#8857)Preview features
Bug fixes
uv lock(#8867)--resolution-mode=lowest-direct(#8839)Documentation
uv python installdocs to use an existing PyPy version (#8845)--verbosewithRUST_LOG(#8858)Install uv 0.5.0
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy ByPass -c "irm https://github.com/astral-sh/uv/releases/download/0.5.0/uv-installer.ps1 | iex"Download uv 0.5.0