5197 commits

Author	SHA1	Message	Date
John Mumm	b06dec8398	Improve Python uninstall perf by removing unnecessary call to installations.find_all() (#14180) ... #13954 introduced an unnecessary slow-down to Python uninstall by calling `installations.find_all()` to discover remaining installations after an uninstall. Instead, we can filter all initial installations against those in `uninstalled`. As part of this change, I've updated `uninstalled` from a `Vec` to an `IndexSet` in order to do efficient lookups in the filter. This required a change I call out below to how we were retrieving them for messaging.	2025-06-23 15:51:44 +02:00
John Mumm	6481aa3e64	Consolidate logic for checking for a virtual environment (#14214) ... We were checking whether a path was an executable in a virtual environment or the base directory of a virtual environment in multiple places in the codebase. This PR consolidates this logic into one place. Closes #13947.	2025-06-23 15:12:43 +02:00
renovate[bot]	3e9dbe8b7d	Update Rust crate mimalloc to v0.1.47 (#14207) ... This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [mimalloc](https://redirect.github.com/purpleprotocol/mimalloc_rust) | dependencies | patch | `0.1.46` -> `0.1.47` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>purpleprotocol/mimalloc_rust (mimalloc)</summary> ### [`v0.1.47`](https://redirect.github.com/purpleprotocol/mimalloc_rust/releases/tag/v0.1.47): Version 0.1.47 [Compare Source](https://redirect.github.com/purpleprotocol/mimalloc_rust/compare/v0.1.46...v0.1.47) ##### Changes - Mimalloc `v2.2.4` </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/astral-sh/uv). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC42Mi4xIiwidXBkYXRlZEluVmVyIjoiNDAuNjIuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiaW50ZXJuYWwiXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-06-23 12:07:09 +02:00
Charlie Marsh	a82c210cab	Add auto-detection for AMD GPUs (#14176) ... ## Summary Allows `--torch-backend=auto` to detect AMD GPUs. The approach is fairly well-documented inline, but I opted for `rocm_agent_enumerator` over (e.g.) `rocminfo` since it seems to be the recommended approach for scripting: https://rocm.docs.amd.com/projects/rocminfo/en/latest/how-to/use-rocm-agent-enumerator.html. Closes https://github.com/astral-sh/uv/issues/14086. ## Test Plan ``` root@rocm-jupyter-gpu-mi300x1-192gb-devcloud-atl1:~# ./uv-linux-libc-11fb582c5c046bae09766ceddd276dcc5bb41218/uv pip install torch --torch-backend=auto Resolved 11 packages in 251ms Prepared 2 packages in 6ms Installed 11 packages in 257ms + filelock==3.18.0 + fsspec==2025.5.1 + jinja2==3.1.6 + markupsafe==3.0.2 + mpmath==1.3.0 + networkx==3.5 + pytorch-triton-rocm==3.3.1 + setuptools==80.9.0 + sympy==1.14.0 + torch==2.7.1+rocm6.3 + typing-extensions==4.14.0 ``` --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-06-21 15:21:06 +00:00
John Mumm	8352560b98	Only update existing symlink directories on preview uninstall (#14179) ... On preview uninstall, we should not create a new minor version symlink directory if one doesn't exist. We should only update existing ones.	2025-06-21 09:50:41 +02:00
Charlie Marsh	0fef253c4b	Use a dedicated type for form metadata (#14175)	2025-06-20 20:33:29 -04:00
Charlie Marsh	e59835d50c	Add XPU to --torch-backend (#14172) ... ## Summary Like ROCm, no auto-detection for now.	2025-06-20 20:33:20 -04:00
Jack O'Connor	0133bcc8ca	(f)lock during uv run (#14153) ... This is very similar to the locking added for `uv sync`, `uv add`, and `uv remove` in https://github.com/astral-sh/uv/pull/13869. Improving our (f)locking in general is tracked in https://github.com/astral-sh/uv/issues/13883.	2025-06-20 20:34:45 +00:00
Zanie Blue	1dbe750452	Refactor PythonVersionFile global loading (#14107) ... I was looking into `uv tool` not supporting version files, and noticed this implementation was confusing and skipped handling like a tracing log if `--no-config` excludes selection a file. I've refactored it in preparation for the next change.	2025-06-20 15:31:32 -05:00
John Mumm	e9d5780369	Support transparent Python patch version upgrades (#13954) ... > NOTE: The PRs that were merged into this feature branch have all been independently reviewed. But it's also useful to see all of the changes in their final form. I've added comments to significant changes throughout the PR to aid discussion. This PR introduces transparent Python version upgrades to uv, allowing for a smoother experience when upgrading to new patch versions. Previously, upgrading Python patch versions required manual updates to each virtual environment. Now, virtual environments can transparently upgrade to newer patch versions. Due to significant changes in how uv installs and executes managed Python executables, this functionality is initially available behind a `--preview` flag. Once an installation has been made upgradeable through `--preview`, subsequent operations (like `uv venv -p 3.10` or patch upgrades) will work without requiring the flag again. This is accomplished by checking for the existence of a minor version symlink directory (or junction on Windows). ### Features * New `uv python upgrade` command to upgrade installed Python versions to the latest available patch release: ``` # Upgrade specific minor version uv python upgrade 3.12 --preview # Upgrade all installed minor versions uv python upgrade --preview ``` * Transparent upgrades also occur when installing newer patch versions: ``` uv python install 3.10.8 --preview # Automatically upgrades existing 3.10 environments uv python install 3.10.18 ``` * Support for transparently upgradeable Python `bin` installations via `--preview` flag ``` uv python install 3.13 --preview # Automatically upgrades the `bin` installation if there is a newer patch version available uv python upgrade 3.13 --preview ``` * Virtual environments can still be tied to a patch version if desired (ignoring patch upgrades): ``` uv venv -p 3.10.8 ``` ### Implementation Transparent upgrades are implemented using: * Minor version symlink directories (Unix) or junctions (Windows) * On Windows, trampolines simulate paths with junctions * Symlink directory naming follows Python build standalone format: e.g., `cpython-3.10-macos-aarch64-none` * Upgrades are scoped to the minor version key (as represented in the naming format: implementation-minor version+variant-os-arch-libc) * If the context does not provide a patch version request and the interpreter is from a managed CPython installation, the `Interpreter` used by `uv python run` will use the full symlink directory executable path when available, enabling transparently upgradeable environments created with the `venv` module (`uv run python -m venv`) New types: * `PythonMinorVersionLink`: in a sense, the core type for this PR, this is a representation of a minor version symlink directory (or junction on Windows) that points to the highest installed managed CPython patch version for a minor version key. * `PythonInstallationMinorVersionKey`: provides a view into a `PythonInstallationKey` that excludes the patch and prerelease. This is used for grouping installations by minor version key (e.g., to find the highest available patch installation for that minor version key) and for minor version directory naming. ### Compatibility * Supports virtual environments created with: * `uv venv` * `uv run python -m venv` (using managed Python that was installed or upgraded with `--preview`) * Virtual environments created within these environments * Existing virtual environments from before these changes continue to work but aren't transparently upgradeable without being recreated * Supports both standard Python (`python3.10`) and freethreaded Python (`python3.10t`) * Support for transparently upgrades is currently only available for managed CPython installations Closes #7287 Closes #7325 Closes #7892 Closes #9031 Closes #12977 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-06-20 16:17:13 +02:00
John Mumm	62365d4ec8	Support netrc and same-origin credential propagation on index redirects (#14126) ... This PR is a combination of #12920 and #13754. Prior to these changes, following a redirect when searching indexes would bypass our authentication middleware. This PR updates uv to support propagating credentials through our middleware on same-origin redirects and to support netrc credentials for both same- and cross-origin redirects. It does not handle the case described in #11097 where the redirect location itself includes credentials (e.g., `https://user:pass@redirect-location.com`). That will be addressed in follow-up work. This includes unit tests for the new redirect logic and integration tests for credential propagation. The automated external registries test is also passing for AWS CodeArtifact, Azure Artifacts, GCP Artifact Registry, JFrog Artifactory, GitLab, Cloudsmith, and Gemfury.	2025-06-20 09:21:32 +02:00
Jack O'Connor	cc8d5a9215	handle an existing shebang in uv init --script (#14141) ... Closes https://github.com/astral-sh/uv/issues/14085.	2025-06-19 14:47:22 -07:00
John Mumm	611a13c841	Fix benchmark compilation failure: cannot find attribute clap in this scope (#14128) ... [Two benchmark jobs](4433771099) were failing with `error: cannot find attribute clap in this scope` based on #14120. This updates the recently added `#[clap(name = rocm...` lines to use `cfg_attr(feature = "clap",`.	2025-06-18 16:30:12 +02:00
konsti	ee0ba65eb2	Unify test venv python command creation (#14117) ... Refactoring in preparation for https://github.com/astral-sh/uv/pull/14080	2025-06-18 15:06:09 +02:00
Charlie Marsh	4d9c9a1e76	Add ROCm backends to --torch-backend (#14120) ... We don't yet support automatic detection, but this at least allows explicit selection (e.g., `uv pip install --torch-backend rocm5.3`). Closes #14087.	2025-06-18 07:35:05 -04:00
Aaron Ang	0cac73dc1f	Warn on empty index directory (#13940) ... Close #13922 ## Summary Add a warning if the directory given by the `--index` argument is empty. ## Test Plan Added test case `add_index_empty_directory` in `edit.rs`	2025-06-18 10:48:21 +02:00
Zanie Blue	47c522f9be	Serialize Python requests for tools as canonicalized strings (#14109) ... When working on support for reading global Python pins in tool operations, I noticed that we weren't using the canonicalized Python request in receipts — we were using the raw string provided by the user. Since we'll need to compare these values, we should be using the canonicalized string. The `Tool` and `ToolReceipt` types have been updated to hold a `PythonRequest` instead of a `String`, and `Serialize` was implemented for `PythonRequest` so canonicalization can happen at the edge instead of being the caller's responsibility.	2025-06-17 17:45:11 -05:00
Charlie Marsh	6c096246d8	Remove preview label from --torch-backend (#14119) ... This is now used in enough places that I'm comfortable committing to maintaining it under our versioning policy. Closes #14091.	2025-06-17 16:49:00 -04:00
Zanie Blue	c25c800367	Fix Ruff linting (#14111)	2025-06-17 17:28:23 +00:00
konsti	10e1d17cfc	Don't use walrus operator in interpreter query script (#14108) ... Fix `uv run -p 3.7` by not using a walrus operator. Python 3.7 isn't really supported anymore, but there's no reason to break interpreter discovery for it.	2025-06-17 12:18:08 -05:00
Andrew Gallant	3d4f0c934e	Fix handling of changes to requires-python (#14076) ... When using `uv lock --upgrade-package=python` after changing `requires-python`, it was possible to get into a state where the fork markers produced corresponded to the empty set. This in turn resulted in an empty lock file. There was already some infrastructure in place that I think was perhaps intended to handle this. In particular, `Lock::check_marker_coverage` checks whether the fork markers have some overlap with the supported environments (including the `requires-python`). But there were two problems with this. First is that in lock validation, this marker coverage check came _after_ a path that returned `Preferable` (meaning that the fork markers should be kept) when `--upgrade-package` was used. Second is that the marker coverage check used the `requires-python` in the lock file and _not_ the `requires-python` in the now updated `pyproject.toml`. We attempt to solve this conundrum by slightly re-arranging lock file validation and by explicitly checking whether the *new* `requires-python` is disjoint from the fork markers in the lock file. If it is, then we return `Versions` from lock file validation (indicating that the fork markers should be dropped). Fixes #13951	2025-06-17 11:50:05 -04:00
John Mumm	e02cd74e64	Turn off clippy::struct_excessive_bools rule (#14102) ... We always ignore the `clippy::struct_excessive_bools` rule and formerly annotated this at the function level. This PR specifies the allow in `workspace.lints.clippy` in `Cargo.toml`.	2025-06-17 12:18:54 +02:00
Zanie Blue	cf67d9c633	Clear XDG_DATA_HOME during test runs (#14075)	2025-06-16 15:01:17 -05:00
konsti	cd71ad1672	Show retries for HTTP status code errors (#13897) ... Using a companion change in the middleware (https://github.com/TrueLayer/reqwest-middleware/pull/235, forked&tagged pending review), we can check and show retries for HTTP status core errors, to consistently report retries again. We fix two cases: * Show retries for status code errors for cache client requests * Show retries for status code errors for Python download requests Not handled: * Show previous retries when a distribution download fails mid-streaming * Perform retries when a distribution download fails mid-streaming * Show previous retries when a Python download fails mid-streaming * Perform retries when a Python download fails mid-streaming	2025-06-16 10:14:00 +00:00
Frazer McLean	87827b6d82	Fix implied platform_machine marker for win_amd64 platform tag (#14041) ... ## Summary Fixes #14040 ## Test Plan Added a test using required-environments	2025-06-15 22:37:40 -04:00
renovate[bot]	4d104dd004	Update Rust crate windows to v0.61.3 (#14055)	2025-06-16 02:05:34 +00:00
Aria Desires	ff9c2c35d7	Support reading dependency-groups from pyproject.tomls with no project (#13742) ... (or legacy tool.uv.workspace). This cleaves out a dedicated SourcedDependencyGroups type based on RequiresDist but with only the DependencyGroup handling implemented. This allows `uv pip` to read `dependency-groups` from pyproject.tomls that only have that table defined, per PEP 735, and as implemented by `pip`. However we want our implementation to respect various uv features when they're available: * `tool.uv.sources` * `tool.uv.index` * `tool.uv.dependency-groups.mygroup.requires-python` (#13735) As such we want to opportunistically detect "as much as possible" while doing as little as possible when things are missing. The issue with the old RequiresDist path was that it fundamentally wanted to build the package, and if `[project]` was missing it would try to desperately run setuptools on the pyproject.toml to try to find metadata and make a hash of things. At the same time, the old code also put in a lot of effort to try to pretend that `uv pip` dependency-groups worked like `uv` dependency-groups with defaults and non-only semantics, only to separate them back out again. By explicitly separating them out, we confidently get the expected behaviour. Note that dependency-group support is still included in RequiresDist, as some `uv` paths still use it. It's unclear to me if those paths want this same treatment -- for now I conclude no. Fixes #13138	2025-06-13 22:16:48 +00:00
Aria Desires	5021840919	Add [tool.uv.dependency-groups].mygroup.requires-python (#13735) ... This allows you to specify requires-python on individual dependency-groups, with the intended usecase being "oh my dev-dependencies have a higher requires-python than my actual project". This includes a large driveby move of the RequiresPython type to uv-distribution-types to allow us to generate the appropriate markers at this point in the code. It also migrates RequiresPython from pubgrub::Range to version_ranges::Ranges, and makes several pub(crate) items pub, as it's no longer defined in uv_resolver. Fixes #11606	2025-06-13 22:04:13 +00:00
konsti	d9b76b97c2	Remove unreachable pub function (#14032) ... Not sure how this landed on main, but rustc complained.	2025-06-13 18:04:13 +00:00
konsti	da2eca4e2c	Make wiremock filter a default filter (#14024) ... Make `127.0.0.1:<PORT>` -> ``[LOCALHOST]`` a general test filter, it simplifies using wiremock and I'm not aware of any false positives.	2025-06-13 08:51:17 -05:00
Zanie Blue	881e17600f	Filter managed Python distributions by platform before querying when included in request (#13936) ... In the case where we have platform information in a Python request, we should filter managed Python distributions by it prior to querying them. Closes https://github.com/astral-sh/uv/issues/13935 --------- Co-authored-by: Aria Desires <aria.desires@gmail.com>	2025-06-13 08:50:44 -05:00
konsti	e10881d49c	Add tests for IO Error retries (#13627) ... Often, HTTP requests don't fail due to server errors, but from spurious network errors such as connection resets. reqwest surfaces these as `io::Error`, and we have to handle their retrying separately. Companion PR: https://github.com/LukeMathWalker/wiremock-rs/pull/159	2025-06-13 09:57:45 +00:00
Zanie Blue	62ed17b230	Bump version to 0.7.13 (#14002)	2025-06-12 14:33:31 -05:00
konsti	7316bd01a3	Build backend: Support namespace packages (#13833) ... Unlike regular packages, specifying all `__init__.py` directories for a namespace package would be very verbose There is e.g. https://github.com/python-poetry/poetry/tree/main/src/poetry, which has 18 modules, or https://github.com/googleapis/api-common-protos which is inconsistently nested. For both the Google Cloud SDK, there are both packages with a single module and those with complex structures, with many having multiple modules due to versioning through `<module>_v1` versioning. The Azure SDK seems to use one module per package (it's not explicitly documented but seems to follow from the process in https://azure.github.io/azure-sdk/python_design.html#azure-sdk-distribution-packages and ccb0e03a3d/doc/dev/packaging.md). For simplicity with complex projects, we add a `namespace = true` switch which disabled checking for an `__init__.py`. We only check that there's no `<module_root>/<module_name>/__init__.py` and otherwise add the whole `<module_root>/<module_name>` folder. This comes at the cost of `namespace = true` effectively creating an opt-out from our usual checks that allows creating an almost entirely arbitrary package. For simple projects with only a single module, the module name can be dotted to point to the target module, so the build still gets checked: ```toml [tool.uv.build-backend] module-name = "poetry.core" ``` ## Alternatives ### Declare all packages We could make `module-name` a list and allow or require declaring all packages: ```toml [tool.uv.build-backend] module-name = ["cloud_sdk.service.storage", "cloud_sdk.service.storage_v1", "cloud_sdk.billing.storage"] ``` Or for Poetry: ```toml [tool.uv.build-backend] module-name = [ "poetry.config", "poetry.console", "poetry.inspection", "poetry.installation", "poetry.json", "poetry.layouts", "poetry.masonry", "poetry.mixology", "poetry.packages", "poetry.plugins", "poetry.publishing", "poetry.puzzle", "poetry.pyproject", "poetry.repositories", "poetry.toml", "poetry.utils", "poetry.vcs", "poetry.version" ] ``` ### Support multiple namespaces We could also allow namespace packages with multiple root level module: ```toml [tool.uv.build-backend] module-name = ["cloud_sdk.my_ext", "local_sdk.my_ext"] ``` For lack of use cases, we delegate this to creating a workspace with one package per module. ## Implementation Due to the more complex options for the module name, I'm moving verification on deserialization later, dropping the source span we'd get from serde. We also don't show similarly named directories anymore. --------- Co-authored-by: Andrew Gallant <andrew@astral.sh>	2025-06-12 17:23:58 +00:00
github-actions[bot]	d9c34259b3	Sync latest Python releases (#13996) ... Automated update for Python releases. --------- Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com> Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-06-12 09:47:28 -05:00
Ahmed Ilyas	a1f9f28762	Do not allow uv add --group ... --script (#13997) ... ## Summary Closes #13988 ## Test Plan `cargo test`	2025-06-12 10:45:12 -04:00
Zanie Blue	806cc5cad9	Debug sync_dry_run flake by panicking with verbose output on failure (#13817) ... Investigating #13744 I tried reproducing here by running the test in a loop, but could not. I presume it's an interaction with other tests. This drops the snapshot, but I think it's worth it to try to examine the flake?	2025-06-12 08:05:25 -05:00
Zanie Blue	87ab57e902	Update the CLI help and reference to include references to the Python bin directory (#13978) ... Closes https://github.com/astral-sh/uv/issues/13977	2025-06-12 10:02:51 +00:00
konsti	b3d7f79770	Universal sync_required_environment_hint test (#13975) ... Use the packse case `no-sdist-no-wheels-with-matching-platform` for a platform independent `sync_required_environment_hint` test. Fixes #13890	2025-06-11 22:47:40 -04:00
Charlie Marsh	81aebf921d	Add zstd and deflate to Accept-Encoding (#13982) ... ## Summary We already pull in these dependencies, so it costs us nothing.	2025-06-11 22:42:47 -04:00
Zanie Blue	f530565323	Use TTY detection to determine if SIGINT forwarding is enabled (#13925) ... Use TTY detection to determine when we should forward SIGINT instead of counting signals, which can lead to various problems where multiple SIGINTs are sent to a child after the first signal. Counting does not make sense in interactive situations that do not exit on interrupt, e.g., the Python REPL. Closes https://github.com/astral-sh/uv/issues/13919 Closes https://github.com/astral-sh/uv/issues/12108	2025-06-11 13:28:34 +00:00
github-actions[bot]	357fc91c3c	Sync latest Python releases (#13956) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-06-10 21:13:32 -05:00
Zanie Blue	4c877b7dc6	Fix generated file change (#13957) ... Regressed in https://github.com/astral-sh/uv/pull/13620 ref failure at 4384658790	2025-06-10 22:03:01 +00:00
Zanie Blue	21986c3fc9	Bump timeout on Python download release fetch (#13955) ... Failing with a 504 at 1556959077 Successful at 4384626025	2025-06-10 16:54:42 -05:00
Zanie Blue	f20a25f91f	Download versions in uv python pin if not found (#13946) ... As another follow-up in the vein of https://github.com/astral-sh/uv/pull/13944, I noticed `uv python pin` doesn't download Python versions, which is a bit weird because we'll warn it's not found.	2025-06-10 10:56:22 -05:00
Zanie Blue	1b82a3ac99	Ignore Python discovery errors during uv python pin (#13944) ... See https://github.com/astral-sh/uv/issues/13935#issuecomment-2957300516 where we fail to write a pin file because we encounter an unusable interpreter. This is actually a special case where `MissingPython` is not raised because we want to show why we failed to find a usable interpreter, which is useful in commands where you _need_ an interpreter to use, but here we don't actually need it. Here, we just log the failure and move on. Related https://github.com/astral-sh/uv/pull/13936	2025-06-10 09:52:23 -05:00
konsti	c54f131500	Add basic network error tests (#13585) ... Add basic tests for error messages on retryable network errors. This test mod is intended to grow to ensure that we handle retryable errors correctly and that we show the appropriate error message if we failed after retrying. The starter tests show some common cases we've seen download errors in: simple and find links indexes, file downloads and Python installs. For `io::Error` fault injection to test the reqwest `Err` path besides the HTTP status code `Ok` path, see https://github.com/LukeMathWalker/wiremock-rs/issues/149.	2025-06-10 12:00:04 +02:00
Jack O'Connor	9129d2a9a3	avoid fetching an exact, cached commit, even if it isn't locked ... Fixes #13513 and #12746.	2025-06-09 23:50:36 +00:00
Jack O'Connor	619132bd8a	make GitOid strict about parsing exactly 40 hex characters	2025-06-09 23:50:36 +00:00
Jack O'Connor	9ff07c113f	add a snapshot test for uv pip install with an exact Git commit	2025-06-09 23:50:36 +00:00