5712 commits

Author	SHA1	Message	Date
Charlie Marsh	c2100d11f3	Make cache control lookups robust to username (#16088) ... ## Summary We serialize the index to the lockfile without the username, so if we compare based on `==` and the user _includes_ the username in their `pyproject.toml`, the check will always fail. Closes https://github.com/astral-sh/uv/issues/16076.	2025-10-01 16:57:50 -04:00
liam	d51a1e7456	Deduplicate marker-specific dependencies in uv pip tree output (#16078) ... Resolves https://github.com/astral-sh/uv/issues/16067 When we build the dependency graph we add an edge per `Requires-Dist`. If a package publishes multiple marker-guarded requirements (like pylint’s `dill>=…` for different Python versions), more than one marker can evaluate to true at runtime, which gives us several edges pointing to the same installed package node. To avoid printing the package multiple times, we gather all edges targeting that node, pass them through a `Cursor`, and aggregate their requirement details before we print the dependency line. That aggregation does two things: 1. If any edge carries a URL, we return that URL immediately. 2. Otherwise we merge all version specifiers into one canonical PEP 440 string. I've added an integration test, namely `cargo test -p uv --test it --features pypi -- no_duplicate_dependencies_with_markers` exercises the new snapshot that installs pylint (with the real dill duplication scenario present in the original issue) and asserts the tree output, both with and without `--show-version-specifiers`, now shows a single dill entry with the merged constraint.	2025-10-01 11:01:41 -05:00
Zanie Blue	8b86bd530e	Remove tracking of inferred dependency conflicts (#15909) ... Alternative to #15884 (see commentary there) Closes https://github.com/astral-sh/uv/issues/15869	2025-10-01 10:03:42 -05:00
Charlie Marsh	ab2f394019	Use a global flags instance for wheel check (#16047) ... ## Summary This stands up the idea proposed in https://github.com/astral-sh/uv/pull/16046/files#r2384395797.	2025-09-30 00:10:11 +00:00
Charlie Marsh	7d9ea797b0	Add UV_SKIP_WHEEL_FILENAME_CHECK to allow installing invalid wheels (#16046) ... ## Summary This PR adds a user setting to allow (in rare cases) accepting wheels with mismatched filenames and internal metadata. Closes https://github.com/astral-sh/uv/issues/8082. Closes https://github.com/astral-sh/uv/issues/15647.	2025-09-29 19:54:25 -04:00
Charlie Marsh	170ab1cd7f	Ignore origin when comparing installed tools (#16055) ... ## Summary This field gets dropped when you serialize and deserialize, so we should ignore it when comparing indexes. Closes https://github.com/astral-sh/uv/issues/16051.	2025-09-29 17:23:18 +00:00
Charlie Marsh	e87236391f	Re-order lock validation checks by severity (#16045) ... ## Summary I don't think it's common for this to matter, but in theory at least it's important that these are ordered by severity. Otherwise, e.g, changing the pre-release mode (and then returning early) could mean we retain the forks when we otherwise shouldn't.	2025-09-29 09:42:21 -04:00
Charlie Marsh	b2cc2c2749	Respect --no-color on the CLI (#16044) ... ## Summary This argument has always existed for compatibility, but apparently we don't respect it. I assume it was unintentionally dropped during a refactor. Closes https://github.com/astral-sh/uv/issues/15950.	2025-09-29 09:38:47 -04:00
Andrei Berenda	1d76c5a365	Add UV_LOG_CONTEXT to EnvironmentOptions (#16031) ... ## Summary Add UV_LOG_CONTEXT to EnvironmentOptions Relates https://github.com/astral-sh/uv/issues/14720 ## Test Plan Tests with existing tests	2025-09-25 21:01:29 +00:00
Andrei Berenda	372283c0cf	Add install_mirrors to EnvironmentOptions (#15937) ... ## Summary Add install_mirrors to EnvironmentOptions Relates #14720 ## Test Plan Tests with existing tests	2025-09-25 10:35:09 -05:00
Zanie Blue	ade2bdbd2a	Bump version to 0.8.22 (#16005)	2025-09-23 14:43:48 -05:00
William Woodruff	92cd9cfb0c	deps: bump astral-tokio-tar to 0.5.5 (#16004)	2025-09-23 13:46:08 -04:00
github-actions[bot]	268f1325ba	Upgrade Pyodide to 0.28.3 (#15999) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-09-23 09:57:15 -05:00
Charlie Marsh	f64da27450	Bump version to v0.8.21 (#16001)	2025-09-23 13:55:19 +00:00
renovate[bot]	9af64cc156	Update Rust crate anyhow to v1.0.100 (#15974) ... Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more [here](https://redirect.github.com/renovatebot/renovate/discussions/37842). This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [anyhow](https://redirect.github.com/dtolnay/anyhow) | workspace.dependencies | patch | `1.0.99` -> `1.0.100` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>dtolnay/anyhow (anyhow)</summary> ### [`v1.0.100`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.100) [Compare Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.99...1.0.100) - Teach clippy to lint formatting arguments in `bail!`, `ensure!`, `anyhow!` ([#&#8203;426](https://redirect.github.com/dtolnay/anyhow/issues/426)) </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:eyJjcmVhdGVkSW5WZXIiOiI0MS45Ny4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjk3LjEwIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJpbnRlcm5hbCJdfQ==--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: konstin <konstin@mailbox.org>	2025-09-23 11:49:23 +00:00
Charlie Marsh	8d6b369274	Refresh lockfile when --refresh is provided (#15991) (#15994) ... ## Summary If you provide `--refresh` to `uv lock`, we'll now always resolve (even though it might return the same result). This is also robust to `--locked` such that `--refresh --locked` will only fail if the lockfile changes. Closes https://github.com/astral-sh/uv/issues/15997.	2025-09-23 07:25:13 -04:00
Charlie Marsh	7f7fac812c	Add S3 request signing (#15925) ... ## Summary This PR enables users to mark a URL as an S3 endpoint, at which point uv will sign requests to that URL by detecting credentials from the standard AWS environment variables, configuration files, etc. Signing is handled by the [reqsign](https://docs.rs/reqsign/latest/reqsign/) crate, which we can also use in the future to sign requests for other providers.	2025-09-22 23:59:52 +00:00
Zanie Blue	3e6fd0b775	Bump version to 0.8.20 (#15998)	2025-09-22 22:34:27 +00:00
Zanie Blue	107d4e0ac7	Add --force flag for uv cache clean (#15992) ... Follows https://github.com/astral-sh/uv/pull/15990 to address concerns there.	2025-09-22 22:15:14 +00:00
Zanie Blue	c21b11edb9	Revert "Refresh lockfile when --refresh is provided (#15991)" (#15993) ... This reverts commit aeb7ee056e from https://github.com/astral-sh/uv/pull/15991 since it will break `uv lock --locked --refresh` otherwise.	2025-09-22 21:13:23 +00:00
Charlie Marsh	aeb7ee056e	Refresh lockfile when --refresh is provided (#15991) ... ## Summary If you provide `--refresh` to `uv lock`, we'll now always resolve (even though it might return the same result).	2025-09-22 15:58:20 -05:00
Zanie Blue	a502464f82	Retain the cache lock and temporary caches during uv run and uvx (#15990) ... We're seeing reports of a regression from https://github.com/astral-sh/uv/pull/15888 where `--no-cache` causes `uv run` and `uvx` to fail to spawn a command. The intent of this code was to allow destructive cache operations _after_ we'd finished setting up the environment. However, it's unclear to me that it's safe to run `uv cache clean` during a `uv run` operation (e.g., `uv run --script` uses an environment in the cache) and, more importantly, we cannot drop non-persistent caches (e.g., from `--no-cache`) as they include the environment we're spawning the command in. Alternative to #15977 which retains release of the lock — we may want to consider that approach still but this regression needs to be resolved quickly. Closes https://github.com/astral-sh/uv/issues/15989 Closes https://github.com/astral-sh/uv/issues/15987 Closes https://github.com/astral-sh/uv/issues/15967	2025-09-22 15:41:07 -05:00
Zanie Blue	1224f65b13	Hide freethreaded+debug Python downloads in uv python list (#15985) ... ref https://github.com/astral-sh/uv/issues/15983#issuecomment-3319579833	2025-09-22 12:24:10 -05:00
Zsolt Dollenstein	46bf420eae	Allow upgrading prerelease versions of the same minor Python version (#15959) ... Turns out if the minor versions matched we returned false from `is_upgrade_of` instead of continuing to compare prerelease versions. Closes #15955. Note: test cases were initially generated by Claude - I tried making them shorter. ## Test plan ``` ❯ cargo run -- -v python upgrade 3.14 [...] DEBUG Inspecting existing executable at `/Users/zsol/.local/bin/python3.14` DEBUG Replacing existing executable for `cpython-3.14.0rc2-macos-aarch64-none` at `/Users/zsol/.local/bin/python3.14` with executable for `cpython-3.14.0rc3-macos-aarch64-none` since it is an upgrade DEBUG Updated executable at `/Users/zsol/.local/bin/python3.14` to cpython-3.14.0rc3-macos-aarch64-none Installed Python 3.14.0rc3 in 5.04s + cpython-3.14.0rc3-macos-aarch64-none (python3.14) [...] ❯ uvx python3.14 -V Python 3.14.0rc3 ```	2025-09-22 16:59:48 +00:00
Zanie Blue	022a8f1dd1	Add test coverage for python_upgrade with a pre-release version (#15982) ... Coverage for https://github.com/astral-sh/uv/pull/15959	2025-09-22 14:26:13 +00:00
Zanie Blue	0edc5677ad	Document support for free-threaded and debug Python versions (#15961) ... Closes #12707 --------- Co-authored-by: Geoffrey Thomas <geofft@ldpreload.com>	2025-09-22 13:59:40 +00:00
konsti	a6daab422f	Add incompatibility from proxy to base package (#15200) ... Add an incompatibility that lets pubgrub skip of marker packages when the base package already has an incompatible version to improve the error messages (https://github.com/astral-sh/uv/issues/15199). The change is also a small perf improvement. Overall this should be able to improve performance in slow cases by avoiding trying proxy package versions that are impossible anyway, for a (ideally very small cost) for tracking the additional incompatibility and tracking the base package for each proxy package. ``` $ hhyperfine --warmup 2 "uv pip compile --universal scripts/requirements/airflow.in" "target/release/uv pip compile --universal scripts/requirements/airflow.in" Benchmark 1: uv pip compile --universal scripts/requirements/airflow.in Time (mean ± σ): 145.5 ms ± 3.9 ms [User: 154.7 ms, System: 140.7 ms] Range (min … max): 139.2 ms … 153.4 ms 20 runs Benchmark 2: target/release/uv pip compile --universal scripts/requirements/airflow.in Time (mean ± σ): 128.7 ms ± 5.5 ms [User: 141.9 ms, System: 137.3 ms] Range (min … max): 121.8 ms … 142.0 ms 23 runs Summary target/release/uv pip compile --universal scripts/requirements/airflow.in ran 1.13 ± 0.06 times faster than uv pip compile --universal scripts/requirements/airflow.in ``` This implementation is the basic version: When we see a proxy `foo{...}>=x,<y` we add a dependency edge `foo{...}>=x,<y` -> `foo>=x,<y`. There are several way to extend this, which likely help more with performance than with error messages. One idea is that if we see `foo{...}>=x,<y` but we already made a selection for `foo==z` outside that range, we can insert a dependency `foo{...}!=z` -> `foo!=z`. This avoids trying any version of the proxy package except the version that matches our previous selection. Another is that if we see a dependency `foo>=x,<y`, we also add `foo{...}>=x,y` -> `foo>=x,<y`. This allows backtracking beyond `foo` immediately if all version of `foo{...}>=x,<y` are incompatible, since `foo{...}>=x,<y` incompatible -> `foo>=x,<y` incompatible -> the package that depended of `foo>=x,<y` is incompatible. The cost for each of these operations is tracking an additional incompatibility per virtual package. An alternative approach is to only add the incompatibility lazily, only when we've tried several version of the virtual package already. This needs to be weighed of with the better error messages that the incompatibility gives, we unfortunately have only few large reference examples. Requires https://github.com/astral-sh/pubgrub/pull/45 Closes https://github.com/astral-sh/uv/issues/15199	2025-09-22 13:26:08 +02:00
github-actions[bot]	3979c59726	Sync latest Python releases (#15958) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-09-20 02:25:21 +00:00
Zanie Blue	fc7c2f8b50	Bump version to 0.8.19 (#15953)	2025-09-19 14:34:41 -05:00
github-actions[bot]	974a83b676	Sync latest Python releases (#15940) ... Add Python 3.13.0rc3 (and some comments in .python-version). Co-authored-by: Geoffrey Thomas <geofft@ldpreload.com>	2025-09-19 18:13:33 +00:00
konsti	00aa2ab672	Make uv cache clean parallel process safe (#15888) ... Currently, `uv cache clean` and `uv cache prune` can cause crashes in other uv processes running in parallel by removing their in-use files. We can solve this by using a shared (read) lock on the cache directory, while the `uv cache` operations use an exclusive (write) lock. The drawback is that this is always one extra lock, and that we assume that all platforms support shared locks. Once Rust 1.89 fulfills our N-2 policy, we can add support for these methods in fs_err and switch to https://doc.rust-lang.org/std/fs/struct.File.html#platform-specific-behavior-2. **Test Plan** Open one terminal, run: ``` uv venv -c -p 3.13 UV_CACHE_DIR=cache uv cache clean UV_CACHE_DIR=cache uv pip install numpy==2.0.0 ``` Open another terminal, run: ``` UV_CACHE_DIR=cache uv cache clean ``` Fixes #15704 Part of #13883	2025-09-19 10:21:22 +02:00
Charlie Marsh	0889d53c25	Bump MSRV to 1.88 (#15935) ... And bump the `rust-toolchain.toml` to `1.90`. Per our versioning policy.	2025-09-18 14:00:39 -04:00
Zanie Blue	4c2d9e19b0	Use EnvVars in linehaul (#15931)	2025-09-18 14:08:58 +00:00
Zanie Blue	e23da5b315	Use EnvVars for Conda variables in tests (#15930)	2025-09-18 07:52:23 -05:00
Frazer McLean	f122387f89	Fix implied platform_machine marker for win_arm64 platform tag (#15921) ... <!-- 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 I'm back again after #14041, this time for `win_arm64`. I [asked a Windows on ARM user](https://github.com/getlogbook/logbook/pull/451#issuecomment-3295513650) what the value of `platform.machine()` is, and it's `ARM64`. ## Test Plan Updated/added tests	2025-09-17 19:33:59 -04:00
Zanie Blue	c4c47814a8	Bump version to 0.8.18 (#15920)	2025-09-17 16:13:41 -05:00
Zanie Blue	fa53a62f0b	Always treat conda environments named base and root as base environments (#15682) ... Extends https://github.com/astral-sh/uv/pull/15679 I'm not sure if we want to do this. It is probably _generally_ true, but I think I'd rather remove the special casing entirely? I think the main case for this is that it could help prevent regressions from #15679 and we can remove it in a breaking release?	2025-09-17 17:32:14 +00:00
Zanie Blue	d5012c66bd	Add handling for unnamed conda environments in base environment detection (#15681) ... While investigating https://github.com/astral-sh/uv/pull/15679, I created an unnamed conda environment and noticed this quality which allows us to detect that it's not the base environment.	2025-09-17 11:34:23 -05:00
Aria Desires	1943aba150	Allow [project] to be missing from a pyproject.toml (#14113) ... Closes #8666 Closes https://github.com/astral-sh/uv/issues/6838 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-17 10:48:56 -05:00
Charlie Marsh	2a14edf75c	Respect UV_INSECURE_NO_ZIP_VALIDATION=1 in duplicate header errors (#15912) ... ## Summary This was just an oversight on these specific returns. Closes https://github.com/astral-sh/uv/issues/15871.	2025-09-17 14:34:49 +00:00
Charlie Marsh	dea1700945	Avoid ANSI codes in debug! messages (#15843) ... ## Summary I spent time trying to figure out how to support this but came up empty. It _seems_ like maybe the `DefaultFields` implementation in `tracing-subscriber` uses debug formatting for fields...? So if you have a string with ANSI codes, they end up printing as unformatted values? I even reverted all our custom formatting in `logging.rs` and saw the same thing. Closes https://github.com/astral-sh/uv/issues/15840.	2025-09-17 14:30:43 +00:00
Charlie Marsh	48f507680c	Add PyG packages to torch backend (#15911) ... ## Summary These are now supported on pyx.	2025-09-17 14:18:30 +00:00
Charlie Marsh	d4806ee921	Re-add triton as a torch backend package (#15910) ... ## Summary This accidentally regressed in https://github.com/astral-sh/uv/pull/15769/files#diff-fcd4a516243929cdb086b7b79af9865a6ed432a0386765b0436392edc17a5a4eL260.	2025-09-17 14:04:50 +00:00
chisato	accfb48876	Fix uv sync --no-sources not switching from editable to registry installations (#15234) ... ## Summary Fixes issue #15190 where `uv sync --no-sources` fails to switch from editable to registry package installations. The problem occurred because the installer's satisfaction check didn't consider the `--no-sources` flag when determining if an existing editable installation was compatible with a registry requirement. ## Solution Modified `RequirementSatisfaction::check()` to reject non-registry installations when `SourceStrategy::Disabled` and the requirement is from registry. Added `SourceStrategy` parameter threading through the entire call chain from commands to the satisfaction check to ensure consistent behavior between `uv sync --no-sources` and `uv pip install --no-sources`. --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-09-17 06:35:32 -05:00
konsti	eb5ec95396	Better warning for no direct build (#15898) ... **Setup** ``` $ git clone https://github.com/wheelnext/variant_aarch64 $ cd variant_aarch64 $ git checkout 1d047e667dbce4c74878a68c653a6b41bc3d3684 ``` **Before** ``` $ uv build -v [...] DEBUG Not using uv build backend direct build of , no pyproject.toml: TOML parse error at line 5, column 1 | 5 | [project] | ^^^^^^^^^ missing field `version` [...] ``` **After** ``` $ uv build -v [...] DEBUG Not using uv build backend direct build of ``, pyproject.toml does not match: The value for `build_system.build-backend` should be `"uv_build"`, not `"flit_core.buildapi"` [...] ``` The empty string gets fixed in https://github.com/astral-sh/uv/pull/15897 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-17 13:18:41 +02:00
Zanie Blue	d805d4a370	Use _CONDA_ROOT to detect conda base environments (#15680) ... While investigating https://github.com/astral-sh/uv/pull/15679, I noticed this variable was available in the environment and seems like a nice additional heuristic.	2025-09-17 11:17:06 +00:00
Zanie Blue	ee5f155f7e	Invert the logic for determining if a path is a base conda environment (#15679) ... Closes https://github.com/astral-sh/uv/issues/15604 The previous logic does not match the discussion in the original issue about this feature, nor does it match the comment for the function. I'm confused because I know this logic is working for some people? I'm consequently a little wary of making this change. I'm following up with some additional changes that should ensure this is robust, e.g., #15680	2025-09-17 06:04:29 -05:00
github-actions[bot]	9ec7971b4a	Add GraalPy 25.0.0 with support for Python 3.12 (#15900) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-09-17 02:54:31 +00:00
Zanie Blue	664eadc59a	Fix verbose logging configuration for flake (#15902) ... Alas in 5054932672 we caught the flake with the assert but the `-vv` flags were not in the right position!	2025-09-17 02:54:12 +00:00
Harshith VH	705b35c552	fix misleading debug message in uv sync (#15881) ... <!-- 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 - Added `RemovableReason` enum to track removal context - Updated `OnExisting::Remove` to include source information - Modified debug message to show appropriate context - Updated all call sites to specify correct removal source fixes: #14734 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-16 18:39:08 +00:00