5197 commits

Author	SHA1	Message	Date
konsti	23261b7e2e	Apply some Edition 2024 fixes (#13479) ... Some `ref`-removal and `use<>` fixes for the Rust Edition 2024 migration, which are also compatible with Rust Edition 2021.	2025-05-16 10:34:22 +02:00
Andrew Pollack	0baa376627	cli: adjust grammar in “script not supported” error (#13483) ... Love this tooling! Small adjustment to help on error messaging 🙏 <!-- 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? --> The previous message was missing the word **“like,”** which made it read a tad awkwardly. This PR inserts the missing word so the error reads naturally: **After:** ``` $ uvx ch1.py error: It looks like you tried to run a Python script at `ch1.py`, which is not supported by `uvx` hint: Use `uv run ch1.py` instead ``` **Before:** ``` $ uvx ch1.py error: It looks you tried to run a Python script at `ch1.py`, which is not supported by `uvx` hint: Use `uv run ch1.py` instead ``` ## Test Plan <!-- How was it tested? --> - `cargo run -- uvx examples/ch1.py` shows the updated message (see “After” above). - `cargo test` passes.	2025-05-16 10:23:30 +02:00
konsti	4aa72089a1	Mask gen as r#gen for the 2024 edition (#13477) ... `gen` is a reserved keyword in Rust 2024. This is a requirement to run `cargo fmt` on the Rust 2024 edition.	2025-05-15 19:21:12 +00:00
Zanie Blue	6fbcd09b5a	Bump version to 0.7.4 (#13473)	2025-05-15 11:08:50 -05:00
Zanie Blue	e92c17881c	Log skip reasons during Python installation key interpreter match checks (#13472) ... Investigating https://github.com/astral-sh/uv/issues/13471	2025-05-15 10:28:01 -05:00
konsti	18a1f0d9db	Build backend: Normalize glob paths (#13465) ... Unlike OS APIs, glob inclusion checks don't work when there are relative path elements such as `./`. We normalize the path before using it for the glob. Fixes #13407	2025-05-15 17:19:02 +02:00
Ahmed Ilyas	7a83f51de2	Reinstall local packages in uv add (#13462) ... ## Summary Closes https://github.com/astral-sh/uv/issues/13388 ## Test Plan `cargo test`	2025-05-15 14:08:54 +00:00
konsti	7261ede004	Refactor build backend testing (#13464) ... This is useful for adding more tests for build backend configuration.	2025-05-15 12:00:02 +00:00
John Mumm	4ea44bec0a	Ensure cached realm credentials are applied if no password is found for index URL (#13463) ... We were not correctly falling back to cached realm credentials when an index URL was provided with only a username. This came up in a [later comment](https://github.com/astral-sh/uv/issues/13443#issuecomment-2881115301) on #13443 where credentials in a pip extra index in `uv.toml` were being ignored when the same URL (but with only a username) was used at the command line for `--extra-index-url`. I've added a test to catch this case. Closes #13443	2025-05-15 13:36:18 +02:00
konsti	12860a9041	Remove extra newline (#13461) ... This left an extra newline the hint, which isn't captured in the snapshot.	2025-05-15 09:30:21 +00:00
Eduardo Rittner Coelho	2d4d93a350	ProgressReporter: align progress bars by largest name length (#13266) ... ## Summary Related to https://github.com/astral-sh/uv/issues/12492 This change makes all progress bars vertically aligned. This is still a WIP and so is not complete, in the current design I store `max_len` in `BarState` and update it on every `on_request_start`, however this is problematic since order matters, and if the largest name is not sent first, the alignment is not complete. To mitigate this we'd probably have to update all previous bars by "iterating" through the `bars` field in `BarState` and update all request bars. Below is an image of what happens when the largest name (`nvidia-cusparselt-cu12`) is not the first (in this case, it was the second to last).  ## Test Plan There are currently no tests, and I'm not sure how to design them since from what I gather the `uv_snapshot` facilities record the final output, not the intermediate stages. --------- Co-authored-by: konstin <konstin@mailbox.org>	2025-05-15 09:32:36 +02:00
Charlie Marsh	b326bb92a0	Retain trailing comments after PEP 723 metadata block (#13460) ... ## Summary Closes https://github.com/astral-sh/uv/issues/13447.	2025-05-14 21:54:20 +00:00
konsti	73cf2b8d59	uv export docs: "export" instead of "install" (#13430) ... Change the two missing places in the `uv export` docs to say "export" instead of "install".	2025-05-13 15:53:10 +02:00
konsti	22b1ed5c5d	Be more precise in unpinned packages warning (#13426) ... Fixes #13424	2025-05-13 07:25:05 +00:00
Charlie Marsh	ca725d08f2	Remove unused source tree variant (#13422) ... ## Summary Perhaps this disappeared when we added support for unnamed requirements?	2025-05-13 07:07:10 +00:00
Charlie Marsh	3b8139526a	Add comma after "i.e." in Conda environment error (#13423)	2025-05-13 03:51:07 +00:00
Charlie Marsh	a179972e2d	Reject pylock.toml in uv add -r (#13421) ... ## Summary This silently fails right now. Closes #13420.	2025-05-13 03:50:01 +00:00
konsti	73d22ac21b	Fix double self-dependency (#13366) ... The fix itself and its documentation live in pubgrub: https://github.com/astral-sh/pubgrub/pull/44 Fixes #13344 --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-05-13 03:03:44 +00:00
konsti	3b125dbe71	Avoid panics for cannot-be-a-base URLs (#13406) ... Following #13376, avoid `.unwrap()` on `Url::path_segments()`. I also added some unwrap-safety comments.	2025-05-12 22:29:26 -04:00
John Mumm	6df588bb00	Redact credentials when displaying URLs (#13333) ... This PR redacts credentials in displayed URLs. It mostly relies on a `redacted_url` function (and where possible `IndexUrl::redacted`). This is a quick way to prevent leaked credentials but it's prone to programmer error when adding new trace statements. A better follow-on would use a `RedactedUrl` type with the appropriate `Display` implementation. This would allow us to still extract credentials from the URL while displaying it securely. On the plus side, the sites where the `redacted_url` function are used serve as easy signposts for where to use the new type in a future PR. Closes #1714.	2025-05-12 18:58:25 +02:00
konsti	1afadda819	Add more context to errors in high level crates. (#13351) ... Add error context in some places where it was previously missing, and a few style improvements.	2025-05-12 11:04:41 +00:00
renovate[bot]	aed9269c8e	Align indentation of long arguments (#13394) ... This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [clap](https://redirect.github.com/clap-rs/clap) | workspace.dependencies | patch | `4.5.35` -> `4.5.38` | --- ### Release Notes <details> <summary>clap-rs/clap (clap)</summary> ### [`v4.5.38`](https://redirect.github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4538---2025-05-11) [Compare Source](https://redirect.github.com/clap-rs/clap/compare/v4.5.37...v4.5.38) ##### Fixes - *(help)* When showing aliases, include leading `--` or `-` ### [`v4.5.37`](https://redirect.github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4537---2025-04-18) [Compare Source](https://redirect.github.com/clap-rs/clap/compare/v4.5.36...v4.5.37) ##### Features - Added `ArgMatches::try_clear_id()` ### [`v4.5.36`](https://redirect.github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4536---2025-04-11) [Compare Source](https://redirect.github.com/clap-rs/clap/compare/v4.5.35...v4.5.36) ##### Fixes - *(help)* Revert 4.5.35's "Don't leave space for shorts if there are none" for now </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:eyJjcmVhdGVkSW5WZXIiOiI0MC43LjEiLCJ1cGRhdGVkSW5WZXIiOiI0MC43LjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbImludGVybmFsIl19--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: konstin <konstin@mailbox.org>	2025-05-12 11:36:48 +02:00
Charlie Marsh	4109210cca	Avoid erroring on pylock.toml dependency entries (#13384) ... ## Summary We want to allow any map; as-is, it expects the unit struct. Closes https://github.com/astral-sh/uv/issues/13383.	2025-05-11 02:55:58 +00:00
Charlie Marsh	e70cf25ea7	Fix .tgz parsing to respect true extension (#13382) ... ## Summary We mapped both `.tgz` and `.tar.gz` to the same enum variant; later, though, we made the assumption that a file marked with that variant ended with exactly `.tar.gz`. Instead, we need to preserve the originating suffix. Closes https://github.com/astral-sh/uv/issues/13372.	2025-05-10 20:55:28 +00:00
Charlie Marsh	d3fc814ff9	Retain dot-separated wheel tags during cache prune (#13379) ... ## Summary If a set of wheel tags includes a dot, this code is treating the part _after_ the dot as an extension, and thereby failing to detect that the entry is a symlink to an archive (and thereby removing the archive). This is all an optimization, so this code just makes it a little targeted: we skip specific known extensions, rather than anything with any extension. Closes https://github.com/astral-sh/uv/issues/13270.	2025-05-10 18:39:11 +00:00
Frazer McLean	62692b4e1b	Fix detection of sorted dependencies when include-group is used (#13354) ... This follows on from #13334 to fix another case. <!-- 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 If a dependency group contained any `{ include-group = "..." }` entries, the sort detection would bail out. The root cause of the problem was gating the sort detection behind `deps.iter().all(Value::is_str)`. A public code search reveals that keeping include-groups at the top is by far the most common, but keeping them at the bottom isn't uncommon. In both of these cases, uv will now preserve the convention that is in use. Unless I've missed it, I don't think uv supports `uv add`ing an include-group, and so that wasn't tested here. ## Test Plan cargo test --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-05-10 14:00:27 -04:00
Zanie Blue	26e37f3a1e	Rename --raw-sources to --raw (#13348) ... This also omits bounds on constraints, and is useful for that. This retains `--raw-sources` as an alias. I've had this on my mind for a while, but https://github.com/astral-sh/uv/pull/12946 reminded me of it again.	2025-05-08 15:05:03 -05:00
Zanie Blue	9a15240147	Fix display of HTTP responses in trace logs for retry of errors (#13339) ... Follows https://github.com/astral-sh/uv/pull/13228 Closes https://github.com/astral-sh/uv/issues/13338 I recall some discussion (maybe around https://github.com/astral-sh/uv/pull/4725) about how finding the source may not work properly? I can't find it though. Now, I tested this, e.g.: ``` ❯ cargo run -q -- pip install anyio -vv --index-url https://download.pytorch.org/whl/torch/ --no-cache --reinstall ... TRACE Considering retry of response HTTP 403 Forbidden for https://download.pytorch.org/whl/torch/anyio/ ``` I lament that I didn't think of that as a testing method in the first place :)	2025-05-08 09:23:24 -05:00
Charlie Marsh	145fe4e7e3	Show 'Downgraded' when self update is used to install an older version (#13340) ... ## Summary Small thing I noticed while testing https://github.com/astral-sh/uv/pull/13305.	2025-05-08 00:17:47 +00:00
Ahmed Ilyas	3eba70cf09	Suggest uv self update if required version is newer (#13305) ... ## Summary Closes #13253 ## Test Plan ```sh ❯ cat pyproject.toml | rg required required-version = ">=0.7.3, <0.8" ❯ cargo run -q --features self-update --manifest-path ~/uv/Cargo.toml add black error: Required uv version `>=0.7.3, <0.8` does not match the running version `0.7.2`. hint: Update `uv` by running `uv self update`. ❯ cat pyproject.toml | rg required required-version = ">=0.7.3" ❯ cargo run -q --features self-update --manifest-path ~/uv/Cargo.toml add black error: Required uv version `>=0.7.3` does not match the running version `0.7.2`. hint: Update `uv` by running `uv self update`. ❯ cat pyproject.toml | rg required required-version = "<0.7" ❯ cargo run -q --features self-update --manifest-path ~/uv/Cargo.toml add black error: Required uv version `<0.7` does not match the running version `0.7.2`. ❯ cat pyproject.toml | rg required required-version = ">=0.4,<0.7" ❯ cargo run -q --features self-update --manifest-path ~/uv/Cargo.toml add black error: Required uv version `>=0.4, <0.7` does not match the running version `0.7.2`. ``` --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-05-08 00:09:29 +00:00
Frazer McLean	d242c47821	Preserve order of dependencies which are sorted naively (#13334) ... ## Summary The prior implementation only looks for dependencies which are sorted by name then specifier. I knew uv was meant to preserve sorted dependencies, but it never seemed to work for me. I've always used the "sort lines" feature of PyCharm/Sublime to sort these lists, and I guess I'm not the only one. In such a case, `flask-wtf>=1.2.1` is sorted before `flask>=3.0.2`. After digging into the code I realised what was happening, hence this merge request. Maybe there's a tool I'm not aware of that people are using to sort dependencies "properly", or are doing it by hand, but I think this is worth supporting. Relevant issues: https://github.com/astral-sh/uv/issues/9076, https://github.com/astral-sh/uv/issues/10738 ## Test Plan `cargo test`	2025-05-07 18:18:20 -04:00
Zanie Blue	3c413f74b9	Bump verison to 0.7.3 (#13337)	2025-05-07 14:37:22 -05:00
Zanie Blue	fa8db5a8d0	Avoid enumerating sources in errors for path Python requests (#13335) ... e.g., these are misleading cruft in the error message at https://github.com/astral-sh/uv/pull/12168#discussion_r2078204601 ``` ❯ uv python find /foo/bar error: No interpreter found for path `/foo/bar` in virtual environments, managed installations, or search path ❯ cargo run -q -- python find /foo/bar error: No interpreter found at path `/foo/bar` ```	2025-05-07 18:53:09 +00:00
konsti	364e3999d4	Improve error message when a virtual environment Python symlink is broken (#12168) ... When removing a Python interpreter underneath an existing venv, uv currently shows a not found error: ``` error: Failed to inspect Python interpreter from active virtual environment at `.venv/bin/python3` Caused by: Python interpreter not found at `/home/konsti/projects/uv/.venv/bin/python3` ``` This is unintuitive, as the file for the Python interpreter does exist, it is a broken symlink that needs to be replaced with `uv venv`. I've been encountering those occasionally, and I expect users that switch between versions a lot will, too, especially when they also use pyenv or a similar Python manager. The new error hints at this solution: ``` error: Failed to inspect Python interpreter from active virtual environment at `.venv/bin/python3` Caused by: Broken symlink at `.venv/bin/python3`, was the underlying Python interpreter removed? hint: To recreate the virtual environment, run `uv venv` ```	2025-05-07 13:24:53 -05:00
konsti	a43333351e	Build backend: Allow escaping in globs (#13313) ... PEP 639 does not allow any characters that aren't in either their limited glob syntax or the alphanumeric Unicode characters. This means there's no way to express a glob such as `**/@test` for the excludes. We extend the glob syntax from PEP 639 by introducing backslash escapes, which can escape all characters but path separators (forward and backwards slashes) to be parsed verbatim. This means we have two glob parsers: The strict PEP 639 parser for `project.license-files`, and our extended parser for `tool.uv`, with a slight difference if you need to use special characters, to both adhere to PEP 639 and to support cases such as #13280. Fixes #13280	2025-05-07 18:31:41 +02:00
Zanie Blue	ddd6f3debe	Fix discovery of pre-release managed Python versions in range requests (#13330) ... We have test coverage for this elsewhere, but managed Python versions are a distinct case because we know the _full_ version before querying the interpreter (whereas, when we find them on the `PATH`, we usually only know `X.y` from the file name). This pre-filter logic now matches our subsequent logic at 060be9cef1/crates/uv-python/src/discovery.rs (L2146-L2149) 060be9cef1 shows the snapshot change.	2025-05-07 09:27:13 -05:00
Tobias Gårdhus	5e7f3d2920	Add --show-with to uv tool list to list packages included by --with (#13264) ... ## Summary Add a `--show-extras` argument to the `uv tool list` cli, to show which extra dependencies were installed with the tool. i.e. ```bash $ uv tool install fastapi --with requests --with typer==0.14 ``` ```bash $ uv tool list --show-extras fastapi v0.115.12 [extras: requests, typer==0.14] - fastapi ``` ## Test Plan Added a new test function based on the others in the same file, with the other arguments tested with the new argument as well.	2025-05-06 15:23:50 -05:00
konsti	1ec1935693	Reproducible uv build backend across operating systems (#13171) ... The goal of this PR is to support reproducible builds and best-effort platform-independent builds. Previously, while the build backend would build the same source dist and wheel on the same machine, they would look different across different operating systems. This PR fixes the platform-dependent walk dir order by sorting and removes platform-specific permissions from the source dist that had caused those differences. The reproducibility goal does not extend to platform-dependent filesystem features, such as permissions and links, especially in interaction with Git. Since most users share code across platforms through Git, we're focusing on cross-platform behavior under Git. One of those caveats is intentional: If a file, such as a bash script, has an executable bit, we preserve it. This means that E.g. builds of Git checkout of a repository with an executable shell script in the sources will have different archives on Unix and Windows. Another relevant case are symlinks: By default, Git on Windows replaces symlinks with a file that contains the path to the target file (https://stackoverflow.com/q/5917249/3549270). (This example comes from Cargo, where it means that the package archive is different on Windows when symlinking license from the repository root to a workspace package) Best reviewed commit-by-commit	2025-05-06 18:51:56 +02:00
Tim Felgentreff	878c2acdf3	Add downloading of GraalPy (#13172) ... ## Summary This adds GraalPy download metadata so that `uv python install graalpy` works. See https://github.com/astral-sh/uv/issues/13114 ## Test Plan The existing integration test was changed to test this functionality.	2025-05-06 11:02:27 -05:00
konsti	9071e0eeac	Move portable glob parsing to struct (#13311) ... Refactoring to make fixing #13280 easier.	2025-05-06 11:22:54 +00:00
konsti	3218e364ae	Use fs_err for paths in symlinking errors (#13303) ... In #13302, there was an IO error without context. This error seems to be caused by a symlink error. Switching as symlinking to `fs_err` ensures these errors will carry context in the future.	2025-05-05 16:29:27 +00:00
Charlie Marsh	f557ea3823	Avoid re-creating virtual environment with --no-sync (#13287) ... ## Summary We now show a user-visible warning if we're using a "stale" virtual environment due to `--no-sync`. I'd also be fine erroring here. Closes https://github.com/astral-sh/uv/issues/13235.	2025-05-05 14:57:46 +00:00
konsti	5386701cc1	Build backend: Make preview default and add configuration docs (#12804) ... Add configuration documentation for the build backend and make it the preview default. The build backend should generally work with default configuration unless you want specific features such as flat layout or module renaming, there is only a dedicated configuration, but no concept or guide page for the build backend. Once the build backend is stable, we can update the guide documentation to explain that uv defaults to its own build backend, but other build backends are also supported. The uv build backend becomes the default in preview, giving it more exposure from users and preparing it to make it the default proper. The current documentation retains warnings that the build backend is in preview. To see current uses of `uv_build` on GitHub: https://github.com/search?q=path%3A**%2Fpyproject.toml+uv_build%3E%3D0&type=code --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-05-05 13:52:31 +00:00
Charlie Marsh	07f346f723	Accept musllinux_1_0 as a valid platform tag (#13289) ... ## Summary This seems to match `packaging`: d0d5ad8687/src/packaging/_musllinux.py (L71C1-L72C62) Closes https://github.com/astral-sh/uv/issues/13045.	2025-05-05 08:53:41 +02:00
Charlie Marsh	2c567a64b9	Treat already-installed base environment packages as preferences in uv run --with (#13284) ... ## Summary If a script has some requirements, and you provide `--with`, we currently ignore any constraints from those requirements. We might want to treat them as hard constraints in the future. For now, though, we just treat them as preferences -- so we _prefer_ those versions, but don't require them to match and still run the `--with` resolution in isolation. Closes https://github.com/astral-sh/uv/issues/13173.	2025-05-04 23:24:57 +00:00
Zanie Blue	ea4284c041	Add --dry-run support to uv self update (#9829) ... See commentary at https://github.com/astral-sh/uv/issues/9828#issuecomment-2537542100 regarding the limitations and future upstream changes needed. ``` ❯ cargo build --features self-update Compiling uv v0.5.8 (/Users/zb/workspace/uv/crates/uv) Finished `dev` profile [unoptimized + debuginfo] target(s) in 7.28s ❯ cp ./target/debug/uv ~/.cargo/bin ❯ uv self update --dry-run info: Checking for updates... Nothing to do. You're on the latest version of uv (v0.5.8) ❯ uv self update --dry-run 0.5.7 info: Checking for updates... Would update uv from v0.5.8 to v0.5.7 ❯ vi ~/.config/uv/uv-receipt.json # Edit the receipt to think its on an older version ❯ uv self update --dry-run info: Checking for updates... Would update uv from v0.5.8 to the latest version ``` --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-05-04 17:54:36 -04:00
Charlie Marsh	c12ce84fbd	Respect locked script preferences in uv run --with (#13283) ... ## Summary Part of https://github.com/astral-sh/uv/issues/13173, but doesn't close the issue. This just respects preferences if your script uses a lockfile, since we already support that for locked _projects_.	2025-05-04 12:56:33 -04:00
konsti	e2d105d045	Retry streaming downloads on broken pipe errors (#13281) ... Educated guess at #12359 See adab70fd9f/src/proto/streams/state.rs (L309-L310) for the error source.	2025-05-04 08:56:15 -04:00
konsti	96cfca1c8f	Move static feature out of perf features (#13265) ... #5577 fixed a bug on macos due to dynamically linking lzma/xz through static linking. In #7686, this feature was moved to the performance category. This PR moves the `xz2/static` back to the general default features, and, inspired by https://github.com/Homebrew/homebrew-core/pull/222211, it structures and documents the feature flags cleaner. We need to take care that this feature does not accidentally disable features we want. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-05-02 15:56:40 +00:00
konsti	b442aae80e	Only rebuild download JSON on change (#13261) ... By default, Cargo runs the build script if any file in the package changes (https://doc.rust-lang.org/cargo/reference/build-scripts.html#change-detection). In our case, we only need to rerun it if `download-metadata.json` changed.	2025-05-02 07:49:34 -05:00