5551 commits

Author	SHA1	Message	Date
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
Zanie Blue	e7c8b47b7a	Clarify messaging when a new resolution needs to be performed (#14938) ... We do not just "ignore" the existing lockfile here. We retain the existing messaging for cases where we do actually throw out the lockfile, like `--upgrade`.	2025-07-29 21:13:30 -04:00
Zanie Blue	11fe8f70f9	Add exclude-newer-package (#14489) ... Adds `exclude-newer-package = { package = timestamp, ... } ` and `--exclude-newer-package package=timestamp`. These take precedence over `exclude-newer` for a given package. This does need to be serialized to the lockfile, so the revision is bumped to 3. I tested a previous version and we can read a lockfile with this information just fine. Closes https://github.com/astral-sh/uv/issues/14394	2025-07-29 17:00:25 -05:00
Zanie Blue	00efde06b6	Split platform detection code into a dedicated uv-platform crate (#14918) ... In service of some subsequent work...	2025-07-28 14:12:04 -05:00
Zanie Blue	5686771464	Cache Python downloads by default in python install tests (#14326) ... Adds a cache bucket for Python installs and uses it by default during tests, extending the opt-in cache added in https://github.com/astral-sh/uv/pull/12175 Updates the `python_install` tests to use a shared cache for Python installs. This reduces the `python_install` test runtime on my machine from 23s -> 17s. The difference should be much larger on machines with slower internet and less cores for test workers :) This should also improve stability in CI by reducing reliance on the network during test runs, see #14327	2025-07-28 17:33:57 +00:00
konsti	ac135278c3	Better warning chain styling (#14934) ... Improve the styling of warning chains for Python installation errors. Apply the same logic to other internal warning and error formatting locations. **Before** <img width="1232" height="364" alt="Screenshot from 2025-07-28 10-06-41" src="https://github.com/user-attachments/assets/e3befe14-ad4c-44ed-8b0a-57d9c9a3b815" /> **After** <img width="1232" height="364" alt="Screenshot from 2025-07-28 10-23-49" src="https://github.com/user-attachments/assets/1bd890c1-5dbb-4662-93bd-14430c060a69" />	2025-07-28 16:23:39 +00:00
shikinamiasuka	55df845922	Fix incorrect file permissions in wheel packages (#14930) ... Fixes #14920 ## Summary Problem: When building wheel packages, metadata files (such as RECORD, METADATA, WHEEL, and license files) were being created with incorrect Unix permissions (--w--wx---), lacking read permissions and having unexpected executable permissions. Solution: The fix ensures that all metadata files in wheel packages are created with proper 644 (rw-r--r--) permissions by: - Adding explicit unix_permissions(0o644) setting in the write_bytes method for metadata files - Updating permission constants to use octal notation for clarity - Improving code comments to document the permission settings Impact: This change ensures wheel packages created by uv have standard file permissions consistent with other Python build tools like setuptools, improving compatibility and following Python packaging best practices.	2025-07-28 15:56:08 +02:00
Zanie Blue	c97d12bcf3	Unhide uv from --build-backend options (#14939) ... Closes https://github.com/astral-sh/uv/issues/14921	2025-07-28 13:26:23 +00:00
renovate[bot]	8cd8c95071	Update Rust crate criterion to 0.7.0 (#14927) ... This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [criterion](https://bheisler.github.io/criterion.rs/book/index.html) ([source](https://redirect.github.com/bheisler/criterion.rs)) | dependencies | minor | `0.6.0` -> `0.7.0` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>bheisler/criterion.rs (criterion)</summary> ### [`v0.7.0`](https://redirect.github.com/bheisler/criterion.rs/blob/HEAD/CHANGELOG.md#070---2025-07-25) [Compare Source](https://redirect.github.com/bheisler/criterion.rs/compare/0.6.0...0.7.0) - Bump version of criterion-plot to align dependencies. </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:eyJjcmVhdGVkSW5WZXIiOiI0MS40MC4wIiwidXBkYXRlZEluVmVyIjoiNDEuNDAuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiaW50ZXJuYWwiXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-07-28 08:10:06 -05:00
konsti	8cb36d6f40	Move all retry tests to network.rs (#14935) ... Retry behavior isn't tied to a specific installation method, but underlies all of them.	2025-07-28 07:33:54 -05:00
Charlie Marsh	0a51489ec4	Remove resolved TODO in allowed_indexes (#14912) ... ## Summary This got solved in #14858.	2025-07-26 04:04:28 +00:00
Zanie Blue	ae1964935f	Remove extra newline (#14907) ... Fixes https://github.com/astral-sh/uv/pull/14905#discussion_r2231915714	2025-07-25 20:40:09 +00:00
Zanie Blue	7b8dd5cfaf	Run cargo update (#14899)	2025-07-25 15:19:38 -05:00
Zanie Blue	396e198081	Update documentation for preview flags (#14902) ... Follows #14823	2025-07-25 15:19:24 -05:00
Zanie Blue	c489fcb633	Update validation for enviroments and required-environments in uv.toml (#14905) ... See https://github.com/astral-sh/uv/pull/14322/files#r2231891679 Closes https://github.com/astral-sh/uv/issues/14904	2025-07-25 15:19:07 -05:00
Zanie Blue	a701d3c447	Use workspace dependencies for crate dev-dependencies (#14903)	2025-07-25 13:57:49 -05:00
Zanie Blue	bfb4bc2aeb	Split preview mode into separate feature flags (#14823) ... I think this would give us better hygiene than a global flag. It makes it easier for users to opt-in to overlapping features, such as Python upgrades and Python bin installations and to disable warnings for preview mode without opting in to a bunch of other features. In general, I want to reduce the burden for putting something under preview. The `--preview` and `--no-preview` flags are retained as global overrides. A new `--preview-features` option is added which accepts comma separated features or can be passed multiple times, e.g., `--preview-features add-bounds,pylock`. There's a `UV_PREVIEW_FEATURES` environment variable for that option (I'm not sure if we should overload `UV_PREVIEW`, but could be convinced).	2025-07-25 11:01:57 -05:00
konsti	9376cf5482	Remove prioritized dist duplication (#14887) ... `Candidate` has an optional field `prioritized`, which was mostly redundant with `CandidateDist`. Specifically, it was only `None`, if `CandidateDist` was `Installed`. This commit removes this duplication.	2025-07-25 17:18:24 +02:00
Charlie Marsh	1146f3f62d	Avoid invalidating lockfile when path or workspace dependencies define explicit indexes (#14876) ... ## Summary This is an alternative to #14003 that takes advantage of the fact that we already validate that the requirements are up-to-date when validating the lockfile, and the requirements for pinned requirements include the index itself -- so rather than collecting all the explicit indexes upfront, we can just add them to the available list as we iterate over the lockfile's dependency graph. This gets all the tests passing from that PR, but with ~no performance impact and a much less invasive change. It also gets the "circular dependency" test passing, which is marked with a TODO in that PR. Closes https://github.com/astral-sh/uv/issues/11419.	2025-07-25 08:18:28 -04:00
Zanie Blue	05031becc3	Fix snapshot for GitHub message (#14881)	2025-07-24 22:40:55 +00:00
Zanie Blue	e48a9c0992	Remove redundant let Some (#14880)	2025-07-24 17:29:56 -05:00
Zanie Blue	cd4cf27d88	Add test cases for dependent conflicting extras (#14879) ... Picked from #9130	2025-07-24 17:29:40 -05:00
Zanie Blue	7e78f54e7c	Bump version to 0.8.3 (#14875)	2025-07-24 15:51:15 -05:00
Zanie Blue	23ed31b94d	Consolidate environment hash filtering (#14864)	2025-07-24 12:35:45 +00:00
konsti	1150de3fc5	uv_build: Allow non-standard entrypoint names (#14867) ... It seems that non-standard entrypoints are still widely used, downgrading the error to a tracing warning. Fixes #14442 --------- Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com>	2025-07-24 14:12:36 +02:00
Elijah Hartvigsen	3b59515614	Fix typos in uv_build reference documentation (#14853) ... ## Summary Fixes both typos mentioned in #14845. ## Test Plan It wasn't :D --------- Co-authored-by: konstin <konstin@mailbox.org>	2025-07-24 09:55:14 +00:00
Charlie Marsh	02e103f867	Respect --with versions over base environment versions (#14863) ... ## Summary This fixes a regression from https://github.com/astral-sh/uv/pull/14447 that we seemingly didn't have test coverage for. Specifically, if you have a version of a package in your project, and then install a different version with `--with`, the environment should import the `--with` version. Closes #14860.	2025-07-24 02:00:03 +00:00
Zanie Blue	1ddfcee9e9	Fix missed stabilization of removal of registry entry during Python uninstall (#14859) ... Funny enough, I caught this via https://github.com/astral-sh/uv/pull/14823	2025-07-23 17:44:48 -05:00