5551 commits

Author	SHA1	Message	Date
konsti	0bde9e4b8f	Read index credentials from env for uv publish (#15545) ... We were previously missing the `index_locations.cache_index_credentials()` call in `uv publish` to load index credentials from the env. See https://github.com/astral-sh/uv/issues/11836#issuecomment-3022735011 Fixes #11836	2025-08-27 11:19:10 -05:00
Zanie Blue	bce30be3a5	Treat a 203 error on credential removal as a missing entry on Windows (#15552) ... Attempting to address the failure at 4900907073	2025-08-27 10:48:12 -05:00
Zsolt Dollenstein	83e42fdd13	Stop setting CLICOLOR_FORCE=1 when calling build backends (#15472) ... ## Summary `CLICOLOR_FORCE` changes the output of underlying build commands, which messes with wrapper tools trying to parse their output. Closes #12564, closes #15415.	2025-08-27 16:28:02 +01:00
Charlie Marsh	9108b04642	Support file or directory removal for Windows symlinks (#15543) ... ## Summary Similar to https://github.com/rust-lang/cargo/pull/13910. I think this should close https://github.com/astral-sh/uv/issues/15541 since we're indiscriminately calling `remove_dir` on that dangling symlink.	2025-08-27 07:43:03 -04:00
konsti	db4dfb4cf9	Add logging to the uv build backend (#15533) ... Add support for `RUST_LOG` to the uv build backend. While we were previously using logging statements in the uv build backend, they could only be shown when when using the direct build fast path through uv, as there was no tracing subscriber to write log messages out. This means no debug logging when using the build backend through pip, `python -m build`, an incompatible version of uv, or any other build frontend; No option to figure why includes and excludes behave the way they do. This PR closes this gap by adding a tracing subscriber. The only option to enable it is `RUST_LOG`, as we don't have a CLI. The formatting style is the same as for uv, and color is also support in the same way, albeit only through anstream's support for TTYs and environment variables. We recommend only `RUST_LOG=uv=debug` and `RUST_LOG=uv=verbose` in the docs, but this can be used to debug into crates such as `glob`, too. <img width="1008" height="325" alt="image" src="https://github.com/user-attachments/assets/d33df219-750b-46a2-b3b4-8895aa137ab9" /> **Before** ``` $ pip wheel . -v [...] Looking in links: /home/konsti/projects/uv/target/wheels/ Processing /home/konsti/projects/uv/scripts/packages/built-by-uv Running command pip subprocess to install build dependencies Looking in links: /home/konsti/projects/uv/target/wheels/ Processing /home/konsti/projects/uv/target/wheels/uv_build-0.8.13-py3-none-manylinux_2_39_x86_64.whl Installing collected packages: uv_build Successfully installed uv_build-0.8.13 Installing build dependencies ... done Running command Getting requirements to build wheel Getting requirements to build wheel ... done Running command Preparing metadata (pyproject.toml) Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: built-by-uv Running command Building wheel for built-by-uv (pyproject.toml) Error: Unsupported glob expression in: `tool.uv.build-backend.*-exclude` Caused by: Invalid character `!` at position 10 in glob: `**/build-*!$§%!½¼²¼³¬!§%$§%.h`. hint: Characters can be escaped with a backslash error: subprocess-exited-with-error × Building wheel for built-by-uv (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. full command: /usr/bin/python3 /usr/lib/python3/dist-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_wheel /tmp/tmpow1illc9 cwd: /home/konsti/projects/uv/scripts/packages/built-by-uv Building wheel for built-by-uv (pyproject.toml) ... error ERROR: Failed building wheel for built-by-uv Failed to build built-by-uv ERROR: Failed to build one or more wheels ``` **After** ``` $ RUST_LOG=uv=debug pip wheel . -v [...] Looking in links: /home/konsti/projects/uv/target/wheels/ Processing /home/konsti/projects/uv/scripts/packages/built-by-uv Running command pip subprocess to install build dependencies Looking in links: /home/konsti/projects/uv/target/wheels/ Processing /home/konsti/projects/uv/target/wheels/uv_build-0.8.13-py3-none-manylinux_2_39_x86_64.whl Installing collected packages: uv_build Successfully installed uv_build-0.8.13 Installing build dependencies ... done Running command Getting requirements to build wheel Getting requirements to build wheel ... done Running command Preparing metadata (pyproject.toml) DEBUG Writing metadata files to /tmp/pip-modern-metadata-l_kh78cj DEBUG Found PEP 639 license declarations, using METADATA 2.4 DEBUG License files match: `LICENSE-APACHE` DEBUG License files match: `LICENSE-MIT` DEBUG License files match: `third-party-licenses/PEP-401.txt` Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: built-by-uv Running command Building wheel for built-by-uv (pyproject.toml) DEBUG Checking metadata directory /tmp/pip-modern-metadata-l_kh78cj/built_by_uv-0.1.0.dist-info DEBUG Found PEP 639 license declarations, using METADATA 2.4 DEBUG License files match: `LICENSE-APACHE` DEBUG License files match: `LICENSE-MIT` DEBUG License files match: `third-party-licenses/PEP-401.txt` DEBUG Writing wheel at /tmp/pip-wheel-bu6to9i7/built_by_uv-0.1.0-py3-none-any.whl DEBUG Wheel excludes: ["__pycache__", "*.pyc", "*.pyo", "build-*!$§%!½¼²¼³¬!§%$§%.h", "/src/built_by_uv/not-packaged.txt"] Error: Unsupported glob expression in: `tool.uv.build-backend.*-exclude` Caused by: Invalid character `!` at position 10 in glob: `**/build-*!$§%!½¼²¼³¬!§%$§%.h`. hint: Characters can be escaped with a backslash error: subprocess-exited-with-error × Building wheel for built-by-uv (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. full command: /usr/bin/python3 /usr/lib/python3/dist-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_wheel /tmp/tmpjrxou13a cwd: /home/konsti/projects/uv/scripts/packages/built-by-uv Building wheel for built-by-uv (pyproject.toml) ... error ERROR: Failed building wheel for built-by-uv Failed to build built-by-uv ERROR: Failed to build one or more wheels ``` (There is no color in the above uv log statements, as pip doesn't register as a TTY) Fixes #12723	2025-08-27 09:14:00 +02:00
Charlie Marsh	2eb1c725aa	Fix failing virtualenv test on Windows (#15542) ... Closes https://github.com/astral-sh/uv/issues/15540.	2025-08-26 23:14:13 -04:00
Charlie Marsh	9eb5fc240c	Refuse to remove non-virtual environments in uv venv (#15538) ... ## Summary Closes https://github.com/astral-sh/uv/issues/15474.	2025-08-26 13:26:20 -04:00
Charlie Marsh	0c674619b2	Avoid erroring when creating venv in current working directory (#15537) ... ## Summary A strange use-case, but the current behavior is definitely a bug. Part of https://github.com/astral-sh/uv/issues/15474.	2025-08-26 12:43:29 -04:00
Charlie Marsh	b2c8f5ef68	Add rkyv implementation for Core Metadata (#15532) ... ## Summary Enables us to store Core Metadata in zero-copy format.	2025-08-26 10:22:50 -04:00
Charlie Marsh	615e076beb	Rename some Simple API structs (#15530) ... ## Summary For clarity.	2025-08-26 13:55:58 +00:00
konsti	439395dadf	Fix unused code warning around entry_from_constructor (#15525)	2025-08-26 13:30:46 +02:00
Harsh Pratap Singh	39537f4372	format {version} on failure (#15527) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary Fixes #15512 ## Test Plan Manually tested : ``` ~/uv/target/release/uv format --version 999.999.999 --preview-features format error: Failed to install ruff 999.999.999 Caused by: Failed to download from: https://github.com/astral-sh/ruff/releases/download/999.999.999/ruff-x86_64-unknown-linux-gnu.tar.gz Caused by: HTTP status client error (404 Not Found) for url (https://github.com/astral-sh/ruff/releases/download/999.999.999/ruff-x86_64-unknown-linux-gnu.tar.gz) ```	2025-08-26 11:26:10 +00:00
github-actions[bot]	75741082f7	Update Pyodide build number to 0.28.2 (#15523) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-26 00:58:20 +00:00
Charlie Marsh	b723129c7c	Clear discovered interpreters when creating virtual environment (#15522) ... ## Summary Closes https://github.com/astral-sh/uv/issues/15518.	2025-08-25 20:24:24 -04:00
Zanie Blue	9b8d6989d4	Allow pinning managed Python versions to specific build versions (#15314) ... Allows pinning the Python build version via environment variables, e.g., `UV_PYTHON_CPYTHON_BUILD=...`. Each variable is implementation specific, because they use different versioning schemes. Updates the Python download metadata to include a `build` string, so we can filter downloads by the pin. Writes the build version to a file in the managed install, e.g., `cpython-3.10.18-macos-aarch64-none/BUILD`, so we can filter installed versions by the pin. Some important follow-up here: - Include the build version in not found errors (when pinned) - Automatically use a remote list of Python downloads to satisfy build versions not present in the latest embedded download metadata Some less important follow-ups to consider: - Allow using ranges for build version pins	2025-08-25 16:25:05 -05:00
Charlie Marsh	b6f1fb7d3f	Respect [pip] settings for uv pip check (#15514) ... ## Summary Oversight from #15486.	2025-08-25 13:47:30 +00:00
Charlie Marsh	ef9a332364	Cache WHEEL and METADATA reads in installed distributions (#15489) ... ## Summary Uses interior mutability to cache the reads. This follows the pattern we use for reading the platform tags in `Interpreter::tags`.	2025-08-25 13:40:20 +00:00
Charlie Marsh	be4d5b72aa	Reject already-installed wheels that don't match the target platform (#15484) ... ## Summary We've received several requests to validate that installed wheels match the current Python platform. This isn't _super_ common, since it requires that your platform changes in some meaningful way (e.g., you switch from x86 to ARM), though in practice, it sounds like it _can_ happen in HPC environments. This seems like a good thing to do regardless, so we now validate that the tags (as recoded in `WHEEL`) are consistent with the current platform during installs. Closes https://github.com/astral-sh/uv/issues/15035.	2025-08-25 09:20:54 -04:00
Pepe Osca	6e802873cc	fix(tests): Refactor uv format tests (#15468) ... Closes #15458 ## Summary Refactor uv format tests to reduce noise.	2025-08-25 07:40:20 -05:00
Charlie Marsh	7f1a464216	Remove redundant STOPSHIPs (#15511) ... ## Summary I accidentally merged these from a partial refactor.	2025-08-25 08:34:47 -04:00
Charlie Marsh	d19d0e26aa	Add --python-platform to uv pip check (#15486) ... ## Summary I want this to facilitate some testing for https://github.com/astral-sh/uv/issues/15035.	2025-08-24 14:14:42 -04:00
Charlie Marsh	99f1f4fee4	Move wheel tag methods to WheelTag (#15487) ... ## Summary Lowering these out of `WheelFilename`.	2025-08-24 14:00:08 -04:00
Charlie Marsh	6d874b1a25	Move WHEEL file parsing into a struct (#15483) ... ## Summary No functional changes, but I need to add more behavior here for https://github.com/astral-sh/uv/issues/15035, so seems nice to do this separately.	2025-08-24 15:53:12 +00:00
Charlie Marsh	f16760e10a	Cache PyTorch wheels by default (#15481) ... ## Summary After chatting with the PyTorch team, it looks like some number of wheels were accidentally uploaded with `no-cache,no-store,must-revalidate` due to https://github.com/pytorch/pytorch/pull/149218. They're going to correct this for the respective wheels. I've encouraged them to set an immutable caching header for these files, and it might happen. But even if this isn't set, by default we only allow these wheels to be cached for 600s, since the other wheels don't include a `Cache-Control` header at all (but do include a `Last-Modified`, so we cache based on our heuristic: `Freshness lifetime heuristically assumed because of presence of last-modified header: 600s`). This probably leads to tons of unnecessary downloads for users over time. Andrey from the PyTorch team agreed that we should do this. Closes https://github.com/astral-sh/uv/issues/15480.	2025-08-24 11:41:17 -04:00
Charlie Marsh	ac84f5aedc	Move preview features into a dedicated crate (#15482) ... ## Summary This is causing some cyclic dependencies issues for me, because these can be used in virtually _any_ crate (like `uv-install-wheel`), which then means that all of `uv-configuration` becomes a dependency, etc. I think this should be a leaf crate so that we can safely depend on it anywhere.	2025-08-24 09:55:30 -04:00
Jorge Hermo	e6def43110	Run the formatter in the project root instead of the working directory (#15440) ... Closes https://github.com/astral-sh/uv/issues/15430 This PR is a branch from https://github.com/astral-sh/uv/pull/15438, opening it as a draft until that is merged to main and I'll merge main with this branch to have a cleaner diff --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-08-22 15:09:42 -05:00
Xavi Simpson	6e2fbbc30f	Add --no-install-local option to uv sync, uv add and uv export (#15328) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary <!-- What's the purpose of the change? What does it do, and why? --> Closes #14866. Adds a `no-install-local` flag to the sync and export commands that excludes locally defined packages from being installed. This helps with if you're caching your virtual environment. You can exclude local packages since they're more likely to change between builds. ## Test Plan snapshot test: `sync::no_install_local` CI ## Notes I made an `InstallOptions` struct to avoid a crate isolation issue I was running into while implementing. Thanks for maintaining this project!	2025-08-22 11:31:52 -05:00
Jorge Hermo	a2d97ae9b1	Respect --project in uv format (#15438) ... Closes https://github.com/astral-sh/uv/issues/15431 This is my first contribution, so I'm sorry if I miss something! Didn't update any documentation nor added tests. Tell me if this is needed for this feature 😄 I will try to address https://github.com/astral-sh/uv/issues/15430 in another PR	2025-08-22 11:27:34 -05:00
Charlie Marsh	93630a8f79	Include cycle error message in uv pip CLI (#15453) ... ## Summary The use of `format!` was dropping the error chain. Closes https://github.com/astral-sh/uv/issues/15397.	2025-08-22 15:30:33 +01:00
Charlie Marsh	088c908cda	Allow more trailing null bytes in zip files (#15452) ... ## Summary There isn't any risk here, and we have reports of at least one zip file with more than one (but fewer than, e.g., 10) null bytes. Closes https://github.com/astral-sh/uv/issues/15451.	2025-08-22 14:50:07 +01:00
Charlie Marsh	3e34aee63e	Avoid introducing unnecessary system dependency on CUDA (#15449) ... ## Summary Packages like `triton` should come from the PyTorch index, but they don't actually vary across (e.g.) the `cu128` or `cu129` indexes. Closes https://github.com/astral-sh/uv/issues/15446. ## Test Plan Validate that the following pins to `cu128`, rather than `cpu`: ``` echo "vllm\ntorch==2.7.1+cu128" | cargo run pip compile --torch-backend=auto --extra-index-url https://wheels.vllm.ai/b2f6c247a9b84556a8ea0e75bb4a2db765ff3315 - --python-platform linux --python-version 3.13 -v ```	2025-08-22 12:06:23 +01:00
Charlie Marsh	b826c8db04	Bump MSRV to 1.87 (#15441) ... ## Summary Per our N-2 policy (1.89 is latest).	2025-08-22 10:21:24 +01:00
Charlie Marsh	35a8dd514e	Import PackageName from uv-normalize (#15439) ... ## Summary This might be unintentional? `PackageName` is re-exported from `uv-pep508`, so some crates import it from there.	2025-08-21 23:15:40 +00:00
Charlie Marsh	91d66e0bd8	Add file-to-CLI overrides for build isolation configuration (#15437) ... ## Summary Like #15395, but `--no-build-isolation`.	2025-08-21 23:54:39 +01:00
Charlie Marsh	d1e0c26678	Add an environment variable for UV_ISOLATED (#15428) ... Closes https://github.com/astral-sh/uv/issues/15427.	2025-08-21 23:39:04 +01:00
Pepe Osca	c4f2da729c	fix(tests): Ensure show_settings tests don't load user config (#15434) ... ## Summary Ensure show_settings tests set XDG_CONFIG_HOME to avoid loading user configuration Closes #15403	2025-08-21 17:10:11 -05:00
Zanie Blue	f210db0907	Fix format doc mistake (#15433)	2025-08-21 21:12:06 +00:00
Charlie Marsh	330b54b173	Add file-to-CLI overrides for reinstall configuration (#15426) ... ## Summary This is like #15395, but for `--reinstall` and `--reinstall-package`.	2025-08-21 19:03:03 +00:00
Zanie Blue	ede75fe628	Bump version to 0.8.13 (#15423)	2025-08-21 13:52:39 -05:00
Charlie Marsh	e4de538dae	Remove UpgradeSelection struct (#15422) ... ## Summary After #15395, I realized that we didn't actually need a separate struct for this since we now pass it around as an `Option`. (The key change from #15395 is that when combining, we treat the options as a single unit.)	2025-08-21 18:35:07 +00:00
Zsolt Dollenstein	11633549fd	extra-build-dependencies: Allow version specifiers if match-runtime is explicitly false (#15420) ... ## Summary `match-runtime` can be explicitly specified, and if it's `false` it should behave the same way as if it's omitted. ## Test Plan Added snapshot test	2025-08-21 17:50:15 +01:00
konsti	25bedeadea	Stop leaking strings in Python downloads (#15418) ... We should not unnecessarily leak memory. Instead, we follow the general patterns and use `Cow` for strings that can be from either a static or a dynamic source.	2025-08-21 17:54:39 +02:00
Charlie Marsh	0397595e53	Treat --upgrade-package on the command-line as overriding upgrade = false in configuration (#15395) ... ## Summary Right now, if you put `upgrade = false` in a `uv.toml`, then pass `--upgrade-package numpy` on the CLI, we won't upgrade NumPy. This PR fixes that interaction by ensuring that when we "combine", we look at those arguments holistically (i.e., we bundle `upgrade` and `upgrade-package` into a single struct, which then goes through the `.combine` logic), rather than combining `upgrade` and `upgrade-package` independently. If approved, I then need to add the same thing for `no-build-isolation`, `reinstall`, `no-build`, and `no-binary`.	2025-08-21 16:20:55 +01:00
youkaichao	b950453891	Add CUDA 12.9 backend (#15416) ... ## Summary Add torch cuda 12.9 backend <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan <!-- How was it tested? --> --------- Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-08-21 16:01:02 +01:00
Charlie Marsh	61e2308806	Add triton to torch-backend manifest (#15405) ... ## Summary The PyTorch team publishes ARM Linux wheels for `triton` to the PyTorch index, which aren't available on PyPI. ## Test Plan ``` echo "torch" | cargo run pip compile - --torch-backend=cu128 --python-platform aarch64-unknown-linux-gnu --python-version 3.13 ``` Previously failed because it couldn't find a compatible `triton` wheel.	2025-08-21 13:23:12 +00:00
Zanie Blue	e31f000da7	Add an experimental uv format command (#15017) ... As a frontend to Ruff's formatter. There are some interesting choices here, some of which may just be temporary: 1. We pin a default version of Ruff, so `uv format` is stable for a given uv version 2. We install Ruff from GitHub instead of PyPI, which means we don't need a Python interpreter or environment 3. We do not read the Ruff version from the dependency tree See https://github.com/astral-sh/ruff/pull/19665 for a prototype of the LSP integration.	2025-08-21 06:33:18 -05:00
Anuraag (Rag) Agrawal	8d6ea3f2ea	Fix uv_build wheel hashes (#15400) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary <!-- What's the purpose of the change? What does it do, and why? --> Currently record hashes are the hex encoded sha-256 sum. However, they're supposed to be urlsafe-base64-nopad. https://packaging.python.org/en/latest/specifications/recording-installed-packages/#the-record-file Fixes #15398 ## Test Plan <!-- How was it tested? --> Build any wheel ``` uv build --wheel ``` Unpack the wheel ``` uvx wheel unpack dist/*.whl ``` Before this change, it will fail with a hash mismatch. I could confirm with a local build that now the wheel can be unpacked with the `wheel` command. While I don't enable hash checking when syncing, presumably it would also currently fail.	2025-08-21 10:54:21 +02:00
github-actions[bot]	f1a023d384	Update Pyodide to 0.28.2 (#15385) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-21 01:04:15 +00:00
Charlie Marsh	fcc8cfc0bc	Add uv sync tests for upgrade CLI interaction (#15396) ... Like #15393 but for `uv sync`, since the settings logic is a bit different than `uv pip`.	2025-08-20 18:31:18 +01:00
Charlie Marsh	1176e5e00c	Retain IO error source in extraction (#15388) ... ## Summary This was accidentally lost in 4f4492dd53.	2025-08-20 16:27:26 +01:00