5579 commits

Author	SHA1	Message	Date
Zanie Blue	ddf2f5ed8c	Remove unused dependencies from uv auth preview refactor (#15589)	2025-09-02 13:16:52 -05:00
Zanie Blue	7162085846	Update messaging for uv auth (#15573) ... To clarify that we are not validating the credentials	2025-09-02 13:16:52 -05:00
Zanie Blue	a68007aa61	Update uv auth snapshots	2025-09-02 13:16:52 -05:00
Zanie Blue	f9e974c1f9	Only allow HTTPS services in login for now (#15559)	2025-09-02 13:16:52 -05:00
Zanie Blue	a1cc12af2b	Add support for credentials in URLs to uv auth (#15554) ... Allows cases like `uv auth login https://username:password@example.com` for coherence with the rest of our interfaces.	2025-09-02 13:16:52 -05:00
Zanie Blue	4ad5ae5e6f	Add preview warnings to native-keyring usage (#15555) ... The refactor here was all done by Claude Code.	2025-09-02 13:16:52 -05:00
Zanie Blue	460ea6e9eb	Add uv auth commands (login, logout, and token) (#15539) ... Picks up the work from - #14559 - https://github.com/astral-sh/uv/pull/14896 There are some high-level changes from those pull requests 1. We do not stash seen credentials in the keyring automatically 2. We use `auth login` and `auth logout` (for future consistency) 3. We add a `token` command for showing the credential that will be used As well as many smaller changes to API, messaging, testing, etc. --------- Co-authored-by: John Mumm <jtfmumm@gmail.com>	2025-09-02 13:16:52 -05:00
Jo Shields	f76e0fe5e6	Add --python-platform riscv64-unknown-linux to various commands (#15630) ... ## Summary We (and I'm sure many others) are currently doing a lot of RISC-V work in QEMU. It is possible to significantly improve the speed of Python-related builds by taking care of the environment setup using an AMD64 `uv` binary (bypassing binfmt/qemu-system emulation). Some approx numbers from local testing in riscv64 Ubuntu in QEMU: | Resolver arch | Command | Time | | --- | --- | --- | | riscv64 | `pip install --upgrade --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 15s | | riscv64 | `uv pip install --upgrade --system --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 5s | | amd64 | `uv pip install --python-platform=riscv64-unknown-linux --upgrade --system --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 4s | The numbers from some larger internal packages with deeper dependency trees are much more pronounced - 3m6 vs 43s vs 8s, in one example. Manylinux 2.39 is specified, as it's the first (only?) RISC-V manylinux ## Test Plan Locally, in QEMU. `$ docker run --platform linux/riscv64 -it ubuntu:latest`, get amd64 libc into LD_LIBRARY_PATH, tests as above	2025-09-02 13:17:30 -04:00
github-actions[bot]	35ce8e1dae	Sync latest Python releases (#15578) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-09-02 14:24:39 +00:00
Michał Górny	4aaf71a38a	Fix python_module test failures w/ system Python and installed uv (#15611) ... ## Summary Override `sys.base_prefix` when performing `python_module` tests, in order to prevent `find_uv_bin()` from finding `uv` installed alongside system Python, and therefore fix test failures on Gentoo. Fixes #15368 ## Test Plan ``` cargo test --profile=fast-build --features git --features pypi --features python --no-default-features --test it python_module ``` Signed-off-by: Michał Górny <mgorny@gentoo.org>	2025-09-02 08:45:14 -05:00
konsti	d5bcc0535a	Add test case for status code retries (#15617) ... When migrating from the `reqwest_retry` crate, we want to ensure that the status codes we retry stay the same. This also helps us to intentionally migrate to a different list later, by enumerating the list of status codes that are retried.	2025-09-02 15:41:54 +02:00
konsti	19e19d5795	Add error trace to invalid package format (#15626) ... In https://github.com/astral-sh/uv/issues/11636, we're getting reports for installation flakes that report an invalid package format for what appears to be a network problem. Since we're cutting the error reporting to the first error message in the chain, we're not reporting the actual network error underneath it. This PR displays the whole error chain for invalid package format errors, so we can debug and eventually catch-and-retry https://github.com/astral-sh/uv/issues/11636.	2025-09-02 15:22:42 +02:00
Charlie Marsh	d70ea34d45	Fix settings rendering for extra-build-dependencies (#15622) ... ## Summary This was fixed in https://github.com/astral-sh/uv/pull/15161, then reverted as it regressed the error handling. I've re-applied the change here, but moved the error handling to the runtime, rather than parse-time. I think this is slightly worse in that we no longer include the originating source code snippet, but it at least gives us the expected behavior :( Closes https://github.com/astral-sh/uv/issues/15124.	2025-09-02 09:06:21 -04:00
adamnemecek	9be016f3f8	refactored IndexUrl (#15613)	2025-09-01 09:28:42 +02:00
adamnemecek	36216363eb	Refactored Refresh::combine (#15609)	2025-08-31 12:18:58 -05:00
konsti	22f80ca00d	Retry streaming Python and bin download errors (#15567) ... When there is an error during the streaming download and unpack for Python interpreter and bin installs, we would previously fail, causing a lot of CI flakes on GitHub Actions. The problem was that the error is not one of the extended IO errors we were previously handling, but a regular reqwest error, nested below layers of errors of other crates processing the stream, including some IO errors. We now handle nested reqwest errors, too. This surfaced another problem: Our manual retry loop couldn't inform the retry middleware that it already performed the limit of retries, and that the middleware should not retry anymore. While too many retries are more a problem for debugging than for the user, this causes confusing error output. To work around this, we disable the retries in the client and handle all retry errors in our loop. Fixes https://github.com/astral-sh/uv/issues/14171 Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-08-31 15:07:22 +00:00
Charlie Marsh	01e5195ef3	Skip non-existent directories in bytecode compilation (#15608) ... ## Summary Closes https://github.com/astral-sh/uv/issues/15577.	2025-08-31 14:53:00 +00:00
Zsolt Dollenstein	c2c713e5d2	fix ecosystem::transformers test (#15605) ... ## Summary This test is broken because faiss-1.8.0.post1's sdist was deleted(?) from [pypi](https://pypi.org/project/faiss-cpu/1.8.0.post1/#files).	2025-08-31 11:55:59 +01:00
konsti	289ed86e63	Use a global BaseClientBuilder (#15548) ... Alternative to #15105 Instead of building a `BaseClientBuilder` from `NetworkSettings` each time we need a client, we instead build a single `BaseClientBuilder` and pass it around. The `RegistryClientBuilder` then uses `BaseClientBuilder` exclusively for configuration. This removes a chunk of copy-and-paste code, and also moves the fallible `retries_from_env` into a single place Borrow vs. clone is mostly ad-hoc, we can change it in either direction if it matters. Closes #15105	2025-08-29 13:30:51 -05:00
konsti	882c9d9482	Make cache_index_credentials() misuse resistant (#15546) ... https://github.com/astral-sh/uv/issues/11836#issuecomment-3022735011 was caused by a missing `cache_index_credentials()` call. This call was always preceding a registry client builder. We can improve this situation by caching index credentials in the registry client builder.	2025-08-29 15:11:54 +00:00
Harsh Pratap Singh	d877899920	Add uv tree --show-sizes to show package sizes (#15531) ... <!-- 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 Adds the enhancement proposed in #15470. Each package in the dependency tree now shows its compressed wheel file size, reading the wheel sizes directly from the lockfile (uv.lock). Doesn't break existing tree formatting or options. If no wheel size is available, nothing is added. Now, developers can identify large packages in their dependency tree. The tree still shows extras exactly as before, and then appends a size for the package. ## Test Plan Manually tested : ``` harsh@fcr-node:~/uv/test-uv-tree-sizes$ ../target/debug/uv tree Using CPython 3.13.7 warning: No `requires-python` value found in the workspace. Defaulting to `>=3.13`. Resolved 4 packages in 6ms pure-python v0.1.0 ├── click v8.2.1 └── six v1.17.0 harsh@fcr-node:~/uv/test-uv-tree-sizes$ ../target/debug/uv tree --show-sizes Using CPython 3.13.7 warning: No `requires-python` value found in the workspace. Defaulting to `>=3.13`. Resolved 4 packages in 6ms pure-python v0.1.0 ├── click v8.2.1 (99.8KiB) └── six v1.17.0 (10.8KiB) ```	2025-08-29 08:31:46 -05:00
Charlie Marsh	4168d9b320	Add --python-platform to uv run and uv tool (#15515) ... ## Summary Closes https://github.com/astral-sh/uv/issues/11120.	2025-08-29 00:51:39 +00:00
Zanie Blue	af856fb883	Bump version to 0.8.14 (#15576)	2025-08-28 21:25:02 +00:00
github-actions[bot]	f461438611	Add managed Python distributions for aarch64-musl (#15574) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-28 15:44:51 -05:00
Zanie Blue	2fd2e19ce3	Use thiserror for keyring error type (#15561)	2025-08-28 08:09:11 -05:00
Zanie Blue	17a86d83ca	Ensure we get the last error from Windows on the same thread (#15564) ... Reverts #15552 Closes https://github.com/astral-sh/uv/pull/15562 Closes https://github.com/astral-sh/uv/issues/15558 The `GetLastError` calls must be on the same thread, or we can pull the wrong last error!	2025-08-27 21:42:37 +00:00
konsti	7d49571336	Rename Dev to Group internally (#15557) ... The "dev" naming is a pre-PEP 735 artifact.	2025-08-27 18:35:43 +00:00
Zanie Blue	9b1328af3d	Lock during installs in uv format to prevent races (#15551) ... Closes https://github.com/astral-sh/uv/issues/15513	2025-08-27 11:42:39 -05:00
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