6550 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Aria Desires	92637c0d0a	more managed	2025-05-23 12:15:33 -04:00
Aria Desires	7e5d135df6	test better?	2025-05-23 11:14:15 -04:00
Aria Desires	dfbc53e326	add regression test	2025-05-23 11:06:12 -04:00
konsti	680392f03f	Update PubGrub to 06ec5a5 (#13616) ... With https://github.com/pubgrub-rs/pubgrub/pull/338 merged, we update PubGrub to 06ec5a5f59ffaeb6cf5079c6cb184467da06c9db	2025-05-23 13:51:43 +00:00
John Mumm	3758c513a4	Remove misleading line in pin documentation (#13611) ... The documentation did not reflect #12921.	2025-05-23 09:04:50 +02:00
konsti	30be27beb1	No GHA token for cross arch tests (#13599)	2025-05-22 21:11:38 +02:00
Aria Desires	8580b4bd2d	Bump version to 0.7.7 (#13601)	2025-05-22 14:42:26 -04:00
konsti	46bc7d3477	Build backend: Support stubs packages (#13563) ... Stubs packages are different in that their name ends with `-stubs`, their module is `<module name>-stubs` (with a dash, not the generally legal underscore) and their modules contain a `__init__.pyi` instead of an `__init__.py` (https://typing.python.org/en/latest/spec/distributing.html#stub-only-packages). We add support in the uv build backend by detecting the `-stubs` suffix. Fixes #13546 --------- Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>	2025-05-22 19:02:17 +02:00
Geoffrey Thomas	c8479574f2	Sync latest Python releases (#13593) ... Pick up python-build-standalone 20250522, in particular to fix astral-sh/python-build-standalone#619	2025-05-22 09:21:44 -04:00
renovate[bot]	c7cabfccd7	Update markdown to v1 and fix CLI reference links (#13166) ... This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [markdown](https://redirect.github.com/wooorm/markdown-rs) | dependencies | major | `0.3.0` -> `1.0.0` | --- ### Release Notes <details> <summary>wooorm/markdown-rs (markdown)</summary> ### [`v1.0.0`](https://redirect.github.com/wooorm/markdown-rs/releases/tag/1.0.0) 💯 Nothing changed since the last alpha. It’s just that: this crate’s now being used a bunch and working well, so it’s time to be stable! </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:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNTcuMyIsInVwZGF0ZWRJblZlciI6IjM5LjI1Ny4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJpbnRlcm5hbCJdfQ==--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: konstin <konstin@mailbox.org>	2025-05-21 22:50:09 +02:00
Michał Górny	dbcfe9f80b	Fix version json tests to work outside git checkout (#13566) ... ## Summary Fix the two version json tests to account for the possibility that uv was built outside a git checkout (e.g. from an unpacked git archive) and therefore does not have the commit info available. This approach uses separate snapshots for the two cases, as suggested in discussion of pull request #13251. Fixes #13212 ## Test Plan 1. `cargo test` in a git clone. 2. `cargo clean`, moved `.git` away, `cargo test` again. --------- Co-authored-by: Aria Desires <aria.desires@gmail.com>	2025-05-21 15:59:39 -04:00
Aria Desires	38884da9b9	make uv version lock and sync (#13317) ... This adopts the logic from `uv remove` for locking and syncing, as the scope of the changes made are ultimately similar. Unlike `uv remove` there is no support for modifying PEP723 scripts, as these are not versioned. In doing this the `version` command gains a truckload of args for configuring lock/sync behaviour. Presumably most of these are passed via settings or env files, and not of particular concern. The most interesting additions are: * `--frozen`: makes `uv version` work ~exactly as it did before this PR * `--locked`: errors if the lockfile is out of date * `--no-sync`: updates the lockfile, but doesn't run the equivalent of `uv sync` * `--package name`: a convenience for referring to a package in the workspace Note that the existing `--dry-run` flag effectively implies `--frozen` for sets and bumps. Fixes #13254 Fixes #13548	2025-05-21 09:46:09 -04:00
konsti	cf27c077be	Remove unnecessary current dir in tests (#13561) ... This is already done by `add_shared_options`.	2025-05-20 21:36:45 +02:00
Charlie Marsh	a47b9fd746	Revert "[docs] Fix Publishing Packages, Next = "Index"" (#13555) ... Reverts astral-sh/uv#13533. I think this isn't quite right. AFAICT, this is actually solved by upgrading our Material version.	2025-05-20 10:35:08 -04:00
Art O Cathain	1bee9320f1	Clarify adding SSH Git dependencies (#13534) ... The current instructions say > prefix a Git-compatible URL (i.e., that you would use with git clone) with git+. But this does not work with the URL that Github gives you when you choose Clone -> SSH via the UI, which is of the form `git@github.com:astral-sh/uv.git`. If you prefix this with `git+`, i.e. `git+git@github.com:astral-sh/uv.git` it does not work. --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-05-20 14:20:15 +00:00
Art O Cathain	9e09482647	[docs] Fix Publishing Packages, Next = "Index" (#13533) ... The Next footer tab on the Publishing Packages docs page just says "Index" which is not helpful. The page it links to is headed "Integration guides".	2025-05-20 10:13:22 -04:00
konsti	bc7b71f269	Platform discovery is using ld.so instead ldd (#13552) ... In platform discovery we're parsing the output of the ELF interpreter, e.g., `/lib64/ld-linux-x86-64.so.2`. This file is ld, not ldd, which was incorrectly named in the code. An alternative is naming everything ELF interpreter instead of ld.so.	2025-05-20 15:27:22 +02:00
Zanie Blue	7f3e94a091	Bump version to 0.7.6 (#13537) ... Co-authored-by: Aria Desires <aria.desires@gmail.com>	2025-05-19 19:46:11 -04:00
konsti	2894721b6e	Use AsyncFn traits for cached client (#13530) ... Make use of the 2024 edition.	2025-05-19 07:49:27 +00:00
renovate[bot]	97d519c9dd	Update Rust crate windows-registry to v0.5.2 (#13528) ... This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [windows-registry](https://redirect.github.com/microsoft/windows-rs) | workspace.dependencies | patch | `0.5.1` -> `0.5.2` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### 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:eyJjcmVhdGVkSW5WZXIiOiI0MC4xMS4xOCIsInVwZGF0ZWRJblZlciI6IjQwLjExLjE4IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJpbnRlcm5hbCJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-05-19 09:32:45 +02:00
renovate[bot]	6b46cb289f	Update pre-commit hook astral-sh/ruff-pre-commit to v0.11.10 (#13520) ... This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [astral-sh/ruff-pre-commit](https://redirect.github.com/astral-sh/ruff-pre-commit) | repository | patch | `v0.11.9` -> `v0.11.10` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. Note: The `pre-commit` manager in Renovate is not supported by the `pre-commit` maintainers or community. Please do not report any problems there, instead [create a Discussion in the Renovate repository](https://redirect.github.com/renovatebot/renovate/discussions/new) if you have any questions. --- ### Release Notes <details> <summary>astral-sh/ruff-pre-commit (astral-sh/ruff-pre-commit)</summary> ### [`v0.11.10`](https://redirect.github.com/astral-sh/ruff-pre-commit/releases/tag/v0.11.10) [Compare Source](https://redirect.github.com/astral-sh/ruff-pre-commit/compare/v0.11.9...v0.11.10) See: https://github.com/astral-sh/ruff/releases/tag/0.11.10 </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:eyJjcmVhdGVkSW5WZXIiOiI0MC4xMS4xOCIsInVwZGF0ZWRJblZlciI6IjQwLjExLjE4IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJpbnRlcm5hbCJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-05-19 09:31:53 +02:00
renovate[bot]	6afb11ccf6	Update Rust crate which to v7.0.3 (#13527)	2025-05-19 00:34:36 +00:00
renovate[bot]	8a404b980f	Update Rust crate toml_edit to v0.22.26 (#13526)	2025-05-19 00:32:43 +00:00
renovate[bot]	e3ade0ff34	Update Rust crate toml to v0.8.22 (#13525)	2025-05-19 00:32:35 +00:00
renovate[bot]	c80ceff151	Update Rust crate boxcar to v0.2.12 (#13522)	2025-05-19 00:28:04 +00:00
renovate[bot]	6842085842	Update Rust crate owo-colors to v4.2.1 (#13524)	2025-05-18 20:27:53 -04:00
renovate[bot]	c3c4586589	Update Rust crate cargo-util to v0.2.20 (#13523)	2025-05-18 20:27:38 -04:00
renovate[bot]	2572ea8754	Update Rust crate bitflags to v2.9.1 (#13521)	2025-05-18 20:27:08 -04:00
samypr100	3483f1d8b3	fix: format uv-trampoline for 2024 edition (#13519) ... ## Summary Follow on to https://github.com/astral-sh/uv/pull/13516 Ensure uv-trampoline is formatted after switching to 2024 edition.	2025-05-18 20:19:27 -04:00
Charlie Marsh	6e05d37a1d	Remove av pin in transformers (#13518) ... ## Summary This test started failing, and it fails at least back to v0.6, so I don't think it's on our end. I'm wondering if all the wheels here were yanked? They're visible in the lockfile, but not on PyPI: https://pypi.org/project/av/9.2.0/#files. So to get this passing, let's just unpin it. Edit: Ahh, ok. It looks like the project ran out of space, so they removed wheels for all the older versions: https://github.com/PyAV-Org/PyAV/issues/1879.	2025-05-18 19:59:34 -04:00
Charlie Marsh	c5032aee80	Bump MSRV to 1.85 and Edition 2024 (#13516) ... ## Summary Builds on https://github.com/astral-sh/uv/pull/11724. Closes https://github.com/astral-sh/uv/issues/13476.	2025-05-18 19:38:43 -04:00
Charlie Marsh	cc6e766232	Update pre-release hint (#13517) ... ## Summary I believe it's a known issue that the "available versions" doesn't respect `--exclude-newer`.	2025-05-18 18:41:18 -04:00
Michał Górny	061751f195	Add missing git feature dep to preserve_executable_bit test (#12850) ... ## Summary Without the `git` feature, it fails with: ``` error: Failed to initialize Git repository at `/home/mgorny/.local/share/uv/tests/.tmp01wGGK/temp/preserve_executable_bit` stdout: stderr: error: `git` operations are not allowed — are you missing a cfg for the `git` feature? ``` ## Test Plan cargo test --features python --profile=fast-build --no-default-features	2025-05-18 17:31:01 -04:00
Charlie Marsh	9904c47daf	Respect default extras in uv remove (#13380) ... ## Summary Using "all extras" in `uv remove` will cause errors for projects with conflicting extras. Now that we have a concept of "default extras", it seems better to respect those defaults like we do for dependency groups. Closes https://github.com/astral-sh/uv/issues/12770.	2025-05-18 17:28:50 -04:00
Reza Gharibi	d4e8df9b94	Fix PowerShell code blocks (#13511) ... <!-- 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 The PowerShell prompt is not `$`, so it is not detected as a `Generic.Prompt` token by Pygments lexers. Therefore, the JavaScript code does not strip the prompt when copying from PowerShell code blocks, such as [here](https://docs.astral.sh/uv/getting-started/installation/#__tabbed_5_2). Other places in the docs have removed the prompt completely to address this issue: * https://docs.astral.sh/uv/guides/projects/#__tabbed_1_2 * https://docs.astral.sh/uv/guides/integration/jupyter/#__tabbed_1_2 This PR updates the PowerShell prompt to `PS>` and changes the code fence language to `pwsh-session` to match the lexer name from [Pygments](https://pygments.org/docs/lexers/#pygments.lexers.shell.PowerShellSessionLexer). This allows the prompt to be correctly detected as a `Generic.Prompt` token and is stripped during copy. Related: https://github.com/astral-sh/uv/pull/12520	2025-05-17 21:06:48 -05:00
Zanie Blue	4b7f5f1103	Update Python releases (#13509)	2025-05-17 13:19:20 -05:00
Eric Nielsen	be1404df2a	Fix VIRTUAL_ENV_PROMPT value in activator/activate (#13501) ... ## Summary <!-- What's the purpose of the change? What does it do, and why? --> I've compared all the activator scripts here with the original ones in https://github.com/pypa/virtualenv/tree/main/src/virtualenv/activation and only the bash/POSIX script here was yielding a VIRTUAL_ENV_PROMPT value with parenthesis and a trailing space, which should be part of the shell prompt (PS1 for bash/POSIX) but not of the VIRTUAL_ENV_PROMPT value itself. This fixes that small inconsistency. Fixes #13456 This reverts commit 0ec2d4e434 ## Test Plan <!-- How was it tested? --> I didn't test this locally.	2025-05-17 07:48:09 -04:00
Charlie Marsh	9d1a14e1f9	Bump version to v0.7.5 (#13500)	2025-05-16 20:37:17 -04:00
konsti	5d37c7ecc5	Apply first set of Rustfmt edition 2024 changes (#13478) ... Rustfmt introduces a lot of formatting changes in the 2024 edition. To not break everything all at once, we split out the set of formatting changes compatible with both the 2021 and 2024 edition by first formatting with the 2024 style, and then again with the currently used 2021 style. Notable changes are the formatting of derive macro attributes and lines with overly long strings and adding trailing semicolons after statements consistently.	2025-05-16 20:19:02 -04:00
konsti	b31d08c683	Bump simple cache bucket to v16 (#13498) ... We broke the rkyv deserialization in e70cf25ea7 (diff-348b24d7a84672ab2873833988156191995ff467619a77f548adbd9808549999L30-R41) by placing `.tar.bz2` in the position of `.tar.gz`. We need to invalidate the cache bucket. Fixes #13492	2025-05-16 20:17:23 -04:00
konsti	316439337f	Don't error when the script is too short for the buffer (#13488) ... I hit this error case with a broken wheel.	2025-05-16 20:14:13 -04:00
konsti	77268ee152	Build backend: Case sensitive module discovery (#13468) ... We may run on case-sensitive file systems (Linux, generally) or on case-insensitive file systems (Windows, generally), while modules in Python may be lower or upper case. For robustness over filesystem casing, we require an explicit module name for modules with upper cases. Fixes #13419	2025-05-16 14:25:35 +02:00
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	dfa1b958ac	Issue template: Please include the complete error message (#13451) ... We're getting a number of user reports where we could have helped if we were just seeing the full error message. If we're not getting an MRE, we should at least urge users to copy the _full_ error they see on screen. 	2025-05-15 07:36:08 -05:00