5428 commits

Author	SHA1	Message	Date
github-actions[bot]	038bf56366	Sync latest Python releases (#15135) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-07 13:59:02 +00:00
konsti	84d57f2ee9	Ensure symlink warning is shown (#15126) ... Fixes #15115, see also https://github.com/clap-rs/clap/discussions/6092 <img width="1079" height="1030" alt="image" src="https://github.com/user-attachments/assets/05b003a6-9ca0-4f2b-8a74-078aa155ce6d" />	2025-08-07 15:56:59 +02:00
Zanie Blue	278295ef02	Add test cases for find_uv_bin (#15110) ... Adds test cases to unblock - https://github.com/astral-sh/uv/pull/14181 - https://github.com/astral-sh/uv/pull/14182 - https://github.com/astral-sh/uv/pull/14184 - https://github.com/astral-sh/uv/pull/14184 - https://github.com/tox-dev/pre-commit-uv/issues/70 We use a package with a symlink to the Python module to get a mock installation of uv without building (or packaging) the uv binary. This lets us test real patterns like `uv pip install --prefix` without encoding logic about where things are placed during those installs. --------- Co-authored-by: konstin <konstin@mailbox.org>	2025-08-07 07:14:01 -05:00
Zanie Blue	aec90f0a3c	Fix warnings when running tests with a subset of features (#15120) ... We were getting dead code warnings on Windows tests because these were not properly feature gated.	2025-08-07 01:28:26 +00:00
Charlie Marsh	3c1844ca4a	Add support for per-project build-time environment variables (#15095) ... ## Summary E.g., you can now do: ```toml [tool.uv.extra-build-variables] flash-attn = { FLASH_ATTENTION_SKIP_CUDA_BUILD = "TRUE" } ```	2025-08-06 18:01:55 -05:00
konsti	59558b13c1	Respect UV_HTTP_RETRIES in uv publish (#15106) ... Previously, publish would always use the default retries, now it respects `UV_HTTP_RETRIES` Some awkward error handling to avoid pulling anyhow into uv-publish.	2025-08-06 17:59:17 +02:00
konsti	52771476f4	Support UV_NO_EDITABLE where --no-editable is supported (#15107) ... Specifically, support `UV_NO_EDITABLE=1 uv export`. It's now also supported in `uv add`, though it's default there anyway and the env var exists only for completeness. Fixes #15103	2025-08-06 13:06:49 +00:00
samypr100	d2330615c4	Update trampoline to ~1.87 nightly (#15052) ... ## Summary 1. Given the upcoming 1.89 update, this bumps uv-trampoline to "~1.87" (closest nightly) from "~1.86" (closest nightly). 2. Adds additional CI check for arm builds now that runners are available. I wasn't sure the MSRV policy applies to uv-trampoline, so I didn't go for higher than ~1.87 nightly. This PR also fixes a build issue starting after 1.87 where fma and fmaf symbols were missing. Temporarily dded `#[allow(clippy::ptr_eq)]` to `close_handles` as this lint should not trigger anymore in 1.88 and above. ## Test Plan Existing tests and local build process. I did not commit the built binaries for security purposes. --------- Co-authored-by: konstin <konstin@mailbox.org>	2025-08-06 12:45:04 +00:00
konsti	91653f5fee	Avoid invalid simplification with conflict markers (#15041) ... Previously, `simplify_conflict_markers` assumed that it can remove all conflict set together, when we need to look at each conflict set individually. Specifically, `(platform_machine == 'x86_64' and extra == 'extra-5-foo-b') or extra == 'extra-5-foo-a'` can't be reduced `platform_machine == 'x86_64'` only because it reduces to true when both conflict extras are activated. This case applied in https://github.com/astral-sh/uv/issues/14805, where a jax 0.5.3 version was used for `platform_machine != 'aarch64' or sys_platform != 'linux'` and the conflict extra `cu128`, but jax 0.7.0 for the conflict extra `cpu`. Only removing the faulty inference regresses lockfiles to much more verbose markers. To balance the much more conservative inference, I added `unify_inference_sets` to simplify cases where all conflict branches reduce to the same marker. This still regresses some markers. For example `sys_platform == 'win32'` regresses to `sys_platform == 'win32' or (extra == 'extra-3-pkg-x1' and extra == 'extra-3-pkg-x2')` in `extra_inferences`, even through x1 and x2 conflict and the second conjunction could be simplified away. Fixes https://github.com/astral-sh/uv/issues/14805	2025-08-06 09:26:26 +00:00
Zanie Blue	ce37286814	Bump version to 0.8.5 (#15093)	2025-08-05 20:21:00 +00:00
adamnemecek	3d3856ffd5	additional use of Self, remove * and & where not needed (#15091) ... continuation of #15074.	2025-08-05 15:19:56 -05:00
Charlie Marsh	bda9ea957a	Support match-runtime = true in the uv pip CLI (#15087) ... ## Summary Pretty straightforward, a ~one line change plus recreating the `BuildDispatch` (which I tried to avoid, but ran into lifetime issues).	2025-08-05 20:03:10 +00:00
Zanie Blue	1fb0fa045c	Add Python versions to markers implied from wheels (#14913) ... Looking into https://github.com/astral-sh/uv/issues/14836 This does resolve the issue, if the user adds `python_version == '3.8.*'` to the `required-environments`.	2025-08-05 14:52:32 -05:00
Zanie Blue	b2e7b2b279	Improve HTTP response caching log messages (#15067) ... "Cached request ... is not storable" doesn't make sense from a user perspective, it's leaking our internal `CachedClient` abstraction. I think it makes more sense to talk about this as "Response from ... is not storable"	2025-08-05 14:34:12 -05:00
adamnemecek	3f83390e34	Make the use of Self consistent. (#15074) ... ## Summary Make the use of `Self` consistent. Mostly done by running `cargo clippy --fix -- -A clippy::all -W clippy::use_self`. ## Test Plan <!-- How was it tested? --> No need.	2025-08-05 20:17:12 +01:00
Charlie Marsh	57f900ad0d	Take a build constraints reference in BuildDispatch (#15090) ... ## Summary This is just more consistent with the other fields.	2025-08-05 18:28:02 +00:00
Charlie Marsh	089b6d5538	Use "option" instead of "setting" in pylock warning (#15089) ... ## Summary We use "option" everywhere else (though I don't have a strong opinion on which is "better").	2025-08-05 18:17:30 +00:00
Charlie Marsh	327af017ae	Remove duplicate extra-build-dependencies warnings for uv pip (#15088) ... ## Summary These are repeated for all the `uv pip` commands.	2025-08-05 19:14:58 +01:00
Charlie Marsh	8ef3b2eb8e	Enable extra build dependencies to 'match runtime' versions (#15036) ... ## Summary This is an alternative to https://github.com/astral-sh/uv/pull/14944 that functions a little differently. Rather than adding separate strategies, you can instead say: ```toml [tool.uv.extra-build-dependencies] child = [{ requirement = "anyio", match-runtime = true }] ``` Which will then enforce that `anyio` uses the same version as in the lockfile.	2025-08-05 19:00:44 +01:00
Charlie Marsh	b2c382f7c1	Revert h2 upgrade (#15079) ... ## Summary While we figure out what's going on in https://github.com/hyperium/h2/issues/856. Closes https://github.com/astral-sh/uv/issues/15056.	2025-08-05 06:55:58 -05:00
Zanie Blue	8db61abb50	Prefer system Python installations over managed ones when --system is used (#15061) ... This fixes a regression from 0.8.0 from https://github.com/astral-sh/uv/pull/7934 and follows https://github.com/astral-sh/uv/pull/15059 The regression is from [this change](https://github.com/astral-sh/uv/pull/7934/files#diff-c7a660ac39628d5e12f388b0cacc7360affa3d7bb21191184d7ee78489675e83), which was made because we'd otherwise (with the other changes in that pull request) _filter out_ managed Python interpreters found in virtual environments. When `--system` is used we'll convert the default Python preference of `managed` to `system` which avoids things like `uv pip install --system` targeting a managed Python installation. The basic test is ``` uv python install uv pip install --system anyio ``` Prior to this change, we'd read a managed interpreter from our managed installation directory and target that. After this change, without #15059, we'd read a managed interpreter from the PATH and target that. Both of those experiences are bad, because the managed interpreters are marked as externally managed. After this change, with #15059, we properly target the system interpreter. Since we use `system` instead of `only-system`, if there is not a system interpreter we'll still retain our existing behavior and use a managed interpreter. This should limit breakage from the change. Given the source of the regression, we could probably use `only-system` here. I don't feel strongly. I think the main benefit of doing so would be that we'd omit the check for managed installations in error messages when an interpreter cannot be found? We can't really add test coverage here because the test suite always has externally managed interpreters :)	2025-08-04 19:53:59 -05:00
Charlie Marsh	c77cb2023f	Show wheel tag hints in install plan (#15066) ... ## Summary If we fail to install a wheel in `uv pip install` that's provided via direct URL, we should explain why, just like in the lockfile.	2025-08-04 23:43:33 +00:00
Charlie Marsh	3b15da3c5d	Enable uv run with a GitHub Gist (#15058) ... ## Summary You can now run `uv run https://gist.github.com/charliermarsh/ea9eab7f56b1b3d41e51960001cae31d` to execute a single-file Gist without having to go in and copy the raw URL.	2025-08-05 00:38:20 +01:00
Charlie Marsh	a28c3fb7d9	Preserve lowered extra build dependencies (#15038) ... ## Summary I should've noticed this during review -- my bad -- but it looks like after lowering, we're converting back to `uv_pep508::Requirement`. This is mostly okay, but it's lossy for some lowerings. For example, we lose index pinning. With this PR, we now preserve the lowered types (`Requirement`). Closes https://github.com/astral-sh/uv/issues/15037.	2025-08-04 22:42:11 +01:00
Zanie Blue	64e91a7e87	Fix handling of python-preference = system when managed interpreters are on the PATH (#15059) ... This is the first part of fixing a 0.8.0 regression from https://github.com/astral-sh/uv/pull/7934 There, we added handling for skipping managed interpreters on the PATH when `only-system` is used, but did not update the logic to prefer system interpreters over managed ones when `system` is used. Here, we fix that by skipping managed interpreters when `system` is used unless _only_ managed interpreters are available. While this logic is applied during in a general discovery method, it's only relevant for the PATH (and the Windows registry) because we already change the _order_ that we inspect installations in when `system` is used, so the managed installation directory is inspected last. This behavior did not regress in 0.8, it's always been this way, however, I need this change in order to fix a different bug.	2025-08-04 16:02:42 +00:00
Zanie Blue	8186aa963f	Remove test case that does not include global exclude newer (#15062) ... Of course, this would flake over time. Follows https://github.com/astral-sh/uv/pull/15054	2025-08-04 15:03:10 +00:00
konsti	06b84c6b60	Fix compile_exclude_newer_package test (#15054)	2025-08-04 09:21:09 +00:00
konsti	2ad924d4cf	Use consistent workspace inheritance (#15031) ... Following a CI failure in https://github.com/astral-sh/uv/pull/15028, ensure that all workspace crates are inheriting the MSRV and other workspace configuration from the workspace root.	2025-08-02 22:03:51 +02:00
Charlie Marsh	a981e92d31	Remove some arguments from install (#15033) ... ## Summary We can read these from `BuildDispatch`.	2025-08-02 19:38:39 +00:00
Charlie Marsh	3a7aeff86f	Respect extra build requires when reading from wheel cache (#15030) ... ## Summary We weren't including these in the cache key when constructing the install plan. We likely still read them from the cache later, but we may have reported the wrong number of prepares, etc.	2025-08-02 19:26:02 +00:00
konsti	368b7b1e12	Fix some nightly lints (#15028) ... Apply fixes for some `cargo check` and `cargo clippy` lints that are on in nightly Rust. The following command now passes, the blanket allows had to many false-positives: ``` cargo +nightly clippy -- -A clippy::doc_markdown -A mismatched_lifetime_syntaxes -A clippy::explicit_deref_methods ``` `cargo +nightly check -- -A mismatched_lifetime_syntaxes` now passes without warnings.	2025-08-02 18:59:23 +00:00
Charlie Marsh	025d209735	Move cache sharding below prepare_metadata_for_build_wheel (#15029) ... ## Summary No change in behavior. This logic just isn't needed until the next block, and as-written, it's hard to tell.	2025-08-02 14:08:49 -04:00
Wang Bing-hua	3dc921d89c	Gracefully handle entrypoint permission errors (#15026) ... Gracefully handle entrypoint permission errors `uv run --with` could fail with a "permission denied" error when it tried to copy an entrypoint with restrictive permissions. For instance: ```sh $ stat -c '%A' /usr/bin/groupmems -rwxr-s--- $ uv python find /usr/bin/python $ uv run --with dummy_test error: failed to open file `/usr/bin/groupmems`: Permission denied (os error 13) ``` The entrypoint copying logic now catches these permission errors and skips the file, making `uv` more resilient on systems with binaries that have restrictive permissions.	2025-08-02 07:03:37 -05:00
Charlie Marsh	785595bd35	Remove retry wrapper when matching on error kind (#14996) ... ## Summary We often match on `ErrorKind` to figure out how to handle an error (e.g., to treat a 404 as "Not found" rather than aborting the program). Unfortunately, if we retry, we wrap the error in a new kind that includes the retry count. This PR adds an unwrapping mechanism to ensure that callers always look at the underlying error. Closes https://github.com/astral-sh/uv/issues/14941. Closes https://github.com/astral-sh/uv/issues/14989.	2025-07-31 17:00:01 -04:00
konsti	56677c540a	Log the debug error trace (#14458) ... For #14425. We can see the error without `error(transparent)` applied by looking at the debug representation.	2025-07-31 19:13:09 +02:00
Zanie Blue	1bca8bd044	Add extra-build-dependencies test cases for setuptools (#14998)	2025-07-31 11:17:53 -05:00
Zanie Blue	d867f3e595	Skipcargo dev generate-all test case in CI (#14972) ... This means that CI tests fail in a way that is redundant with the dedicated CI job which can obscure signal on whether actual tests are failing e.g., 4703411653	2025-07-31 15:49:42 +00:00
Charlie Marsh	fa24d9a5e2	Include wheel hashes from local Simple indexes (#14993) ... ## Summary This just looks like an oversight. We weren't including hashes from local Simple API indexes if a package had both a wheel and a source distribution. Closes https://github.com/astral-sh/uv/issues/14883	2025-07-31 14:20:49 +00:00
Chisato	538ebe6fcf	Fix symlink preservation in virtual environment creation (#14933) ... ## Summary Fixes inconsistent symlink handling in `uv venv` command (#14670). ## Problem 00efde06b6/crates/uv-virtualenv/src/virtualenv.rs (L81) The original code used `Path::metadata()` which automatically follows symlinks, causing the system to treat symlinked virtual environment paths as regular directories. When a user runs uv venv on an existing symlinked virtual environment `(.venv -> foo)`, the code incorrectly treats the symlink as a regular directory because `location.metadata()` automatically follows the symlink and returns metadata for the target directory `foo/`. This causes the removal logic to delete the symlink itself and permanently breaking the symlink relationship and replacing it with a standard directory structure. ## Solution - Use canonicalize() to resolve symlinks only when removing and recreating virtual environments - This ensures operations target the actual directory while preserving the symlink structure - Minimal change that fixes the core issue without complex path management ## Test Plan ```bash ➜ test-env alias uv-dev='/Users/wingmunfung/workspace/uv/target/debug/uv' ➜ test-env ln -s dummy foo ➜ test-env ln -s foo .venv ➜ test-env ls -lah total 0 drwxr-xr-x 4 wingmunfung staff 128B Jul 30 10:39 . drwxr-xr-x 48 wingmunfung staff 1.5K Jul 29 17:08 .. lrwxr-xr-x 1 wingmunfung staff 3B Jul 30 10:39 .venv -> foo lrwxr-xr-x 1 wingmunfung staff 5B Jul 30 10:39 foo -> dummy ➜ test-env uv-dev venv Using CPython 3.13.2 Creating virtual environment at: .venv error: Failed to create virtual environment Caused by: failed to create directory `.venv`: File exists (os error 17) ➜ test-env mkdir dummy ➜ test-env uv-dev venv Using CPython 3.13.2 Creating virtual environment at: .venv Activate with: source .venv/bin/activate ➜ test-env ls -lah total 0 drwxr-xr-x 5 wingmunfung staff 160B Jul 30 10:39 . drwxr-xr-x 48 wingmunfung staff 1.5K Jul 29 17:08 .. lrwxr-xr-x 1 wingmunfung staff 3B Jul 30 10:39 .venv -> foo drwxr-xr-x 7 wingmunfung staff 224B Jul 30 10:39 dummy lrwxr-xr-x 1 wingmunfung staff 5B Jul 30 10:39 foo -> dummy ➜ test-env uv-dev venv Using CPython 3.13.2 Creating virtual environment at: .venv ✔ A virtual environment already exists at `.venv`. Do you want to replace it? · yes Activate with: source .venv/bin/activate ➜ test-env ls -lah total 0 drwxr-xr-x 5 wingmunfung staff 160B Jul 30 10:39 . drwxr-xr-x 48 wingmunfung staff 1.5K Jul 29 17:08 .. lrwxr-xr-x 1 wingmunfung staff 3B Jul 30 10:39 .venv -> foo drwxr-xr-x@ 7 wingmunfung staff 224B Jul 30 10:39 dummy lrwxr-xr-x 1 wingmunfung staff 5B Jul 30 10:39 foo -> dummy ### the symlink still exists ``` --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-07-31 11:59:23 +00:00
Charlie Marsh	3564e882d7	Ensure consistent indentation when adding dependencies (#14991) ... ## Summary The basic problem here is that when we had multiple items in an inline array, and that array expanded to multiple lines, we accidentally changed the indentation part-way through due to how prefixes work in the TOML. Here's Claude's explanation of the root cause, which I find pretty decent: ``` Here's what happened step by step: 1. First item ("iniconfig"): Has empty prefix "" → indentation_prefix stays None → uses default 4 spaces 2. Second item ("ruff"): Has empty prefix "" → indentation_prefix stays None → uses default 4 spaces 3. Third item ("typing-extensions"): Has prefix " " (single space from inline format) → indentation_prefix becomes Some(" ") → uses only 1 space! This produced: [dependency-groups] dev = [ "iniconfig>=2.0.0", "ruff", "typing-extensions", # ← Only 1 space instead of 4! ] Why the Third Item Had a Different Prefix In inline arrays like ["ruff", "typing-extensions"], the items are separated by commas and spaces. When parsed by the TOML library: - "ruff" has no prefix (it comes right after [) - "typing-extensions" has a single space prefix (the space after the comma) The Fix Moving the indentation calculation outside the loop ensures it's calculated only once: // Calculate indentation ONCE before the loop if let Some(first_item) = deps.iter().next() { let decor_prefix = /* get prefix from first item */ indentation_prefix = (!decor_prefix.is_empty()).then_some(decor_prefix.to_string()); } // Now use the same indentation for ALL items for item in deps.iter_mut() { // Apply consistent indentation to every item } This ensures all items get the same indentation (4 spaces by default when converting from inline arrays), producing the correct output: [dependency-groups] dev = [ "iniconfig>=2.0.0", "ruff", "typing-extensions", # ← Correct 4-space indentation ] The bug only affected arrays being converted from inline to multiline format, where different items might have different residual formatting from their inline representation. ``` Closes #14961. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-07-31 11:50:05 +00:00
Tim de Jager	fc0f637406	Make the BuildDispatch interpreter method async (#14956) ... This is a bit of a weird request, but in [pixi](https://pixi.sh) we are making use of this function to lazily instantiate a conda environment. Well, in actuality we are using a shim to the `BuildDispatch` to actually to only create a conda prefix, if some package needs to be built during the resolution phase. Otherwise we can resolve everything without an enviroment containing a python intepreter. We are using a method now - that uses the runtime to run async code inside this function, as `interpreter` is the first method called on a `BuildContext` when running a source build - using `tokio::Handle::block_on`. However was causing a deadlock in very specific situations, me and @baszalmstra + @wolfv have investigated this thoroughly, but have not been able to find the root cause. It would hang in a part of the uv code that hits the index, but that is **after** all of our initialization *and the blocking call* was completed. Changing this to be fully async fixes the problem, this requires this method to be async though. We get that this is not necessarily required, and we might find a workaround, but I wanted to try it this way first. Thanks!	2025-07-31 06:42:27 -05:00
Aaron Ang	3df972f18a	Support installing additional executables in uv tool install (#14014) ... Close #6314 ## Summary Continuing from #7592. Created a new PR to rebase the old branch with `main`, cleaned up test errors, and improved readability. ## Test Plan Same test cases as in #7592. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-07-30 14:50:24 -05:00
Zanie Blue	e176e17144	Bump version to 0.8.4 (#14980)	2025-07-30 16:24:20 +00:00
Zanie Blue	630394476e	Copy entrypoints that have a shebang that differs in python vs python3 (#14970) ... In https://github.com/astral-sh/uv/issues/14919 it was reported that uv's behavior differed after the first invocation. I noticed we weren't copying entrypoints after the first invocation. It turns out the shebangs were written with `.../python` but on a subsequent invocation the `sys.executable` was `.../python3` so we didn't detect these as matching. This is a pretty naive fix, but it seems much easier than ensuring the entry point path exactly matches the subsequent `sys.executable` we find. I guess we should fix this in reverse too? but I think we might always prefer `python3` when loading interpreters from environments. See #14790 for more background.	2025-07-30 11:00:16 -05:00
Zanie Blue	c9d3d60a18	Implement CacheKey for all Pep508Url variants (#14978) ... Closes #14973	2025-07-30 10:44:06 -05:00
Charlie Marsh	a76e538aa5	Extend wheel filtering to Android tags (#14977) ... ## Summary Just while I'm here for https://github.com/astral-sh/uv/pull/14976.	2025-07-30 15:26:44 +00:00
Charlie Marsh	9b8ff44a04	Perform wheel lockfile filtering based on platform and OS intersection (#14976) ... ## Summary Ensures that if the user filters to macOS ARM, we don't include macOS x86_64 wheels. Closes https://github.com/astral-sh/uv/issues/14901.	2025-07-30 15:12:22 +00:00
Zanie Blue	6856a27711	Add extra-build-dependencies (#14735) ... Replaces https://github.com/astral-sh/uv/pull/14092 Adds `tool.uv.extra-build-dependencies = {package = [dependency, ...]}` which extends `build-system.requires` during package builds. These are lowered via workspace sources, are applied to transitive dependencies, and are included in the wheel cache shard hash. There are some features we need to follow-up on, but are out of scope here: - Preferring locked versions for build dependencies - Settings for requiring locked versions for build depencies There are some quality of life follow-ups we should also do: - Warn on `extra-build-dependencies` that do not apply to any packages - Add test cases and improve error messaging when the `extra-build-dependencies` resolve fails ------- There ~are~ were a few open decisions to be made here 1. Should we resolve these dependencies alongside the `build-system.requires` dependencies? Or should we resolve separately? (I think the latter is more powerful? because you can override things? but it opens the door to breaking your build) 2. Should we install these dependencies into the same environment? Or should we layer it on top as we do elsewhere? (I think it's fine to install into the same environment) 3. Should we respect sources defined in the parent project? (I think yes, but then we need to lower the dependencies earlier — I don't think that's a big deal, but it's not implemented) 4. Should we respect sources defined in the child project? (I think no, this gets really complicated and seems weird to allow) 5. Should we apply this to transitive dependencies? (I think so) --------- Co-authored-by: Aria Desires <aria.desires@gmail.com> Co-authored-by: konstin <konstin@mailbox.org>	2025-07-30 09:53:07 -05:00
Boseong Choi	b2eff990df	Fix typo in uv-pep440/README.md (#14965) ... ## Summary I noticed what appears to be a small typo in the documentation. In the section describing dev versions, it says `sbpth table releases`. I believe this was meant to be `both stable releases`, to match the structure of the previous sentence about post versions.	2025-07-30 12:25:48 +02:00
Charlie Marsh	b31d786fe9	Add UV_ prefix to installer environment variables (#14964) ... ## Summary Available as of https://github.com/astral-sh/cargo-dist/pull/46.	2025-07-30 01:24:59 +00:00