424 commits

Author	SHA1	Message	Date
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
Zanie Blue	e23da5b315	Use EnvVars for Conda variables in tests (#15930)	2025-09-18 07:52:23 -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
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
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	8f3583a6e6	Allow selection of debug build interpreters (#11520) ... Extends the `PythonVariant` logic to support interpreters with the debug flag enabled.	2025-09-12 13:32:22 +00:00
David Peter	0d174b79e2	Ignore pre-release versions in uv init --script (#15747) ... ## Summary Ignore managed pre-release versions of Python for purposes of creating a `requires-python` constraint when running `uv init --script`. This makes the behavior consistent with `uv init` for normal projects. ## Test Plan Added a regression test that makes sure that the constraint is `requires-python = ">=3.13"`, even though a pre-release version of 3.14 is installed.	2025-09-10 14:35:29 -05:00
konsti	cd49e1d11f	Use the windows crate facade consistently (#15737) ... The initial motivation for this change was that we were using both the `windows`, the `window_sys` and the `windows_core` crate in various places. These crates have slightly unconventional versioning scheme where there is a large workspace with the same version in general, but only some crates get breaking releases when a new breaking release happens, the others stay on the previous breaking version. The `windows` crate is a shim for all three of them, with a single version. This simplifies handling the versions. Using `windows` over `windows_sys` has the advantage of a higher level error interface, we now get a `Result` for all windows API calls instead of C-style int-returns and get-last-error calls. This makes the uv-keyring crate more resilient. We keep using the `windows_registry` crate, which provides a higher level interface to windows registry access.	2025-09-09 15:07:14 +00:00
Zanie Blue	e136a51f3d	Skip Python interpreters that cannot be queried with permission errors (#15685) ... Closes https://github.com/astral-sh/uv/issues/15651	2025-09-05 09:03:41 -05:00
github-actions[bot]	4162005df8	Sync latest Python releases (#15670) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-09-03 20:04:55 -05:00
github-actions[bot]	8fcd88d2d4	Sync latest Python releases (#15631) ... Update to python-build-standalone 20250902 mostly for SQLite 3.50.4/CVE-2025-6965.	2025-09-02 18:43:17 +00:00
github-actions[bot]	35ce8e1dae	Sync latest Python releases (#15578) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-09-02 14:24:39 +00:00
konsti	22f80ca00d	Retry streaming Python and bin download errors (#15567) ... When there is an error during the streaming download and unpack for Python interpreter and bin installs, we would previously fail, causing a lot of CI flakes on GitHub Actions. The problem was that the error is not one of the extended IO errors we were previously handling, but a regular reqwest error, nested below layers of errors of other crates processing the stream, including some IO errors. We now handle nested reqwest errors, too. This surfaced another problem: Our manual retry loop couldn't inform the retry middleware that it already performed the limit of retries, and that the middleware should not retry anymore. While too many retries are more a problem for debugging than for the user, this causes confusing error output. To work around this, we disable the retries in the client and handle all retry errors in our loop. Fixes https://github.com/astral-sh/uv/issues/14171 Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-08-31 15:07:22 +00:00
github-actions[bot]	f461438611	Add managed Python distributions for aarch64-musl (#15574) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-28 15:44:51 -05:00
github-actions[bot]	75741082f7	Update Pyodide build number to 0.28.2 (#15523) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-26 00:58:20 +00:00
Charlie Marsh	b723129c7c	Clear discovered interpreters when creating virtual environment (#15522) ... ## Summary Closes https://github.com/astral-sh/uv/issues/15518.	2025-08-25 20:24:24 -04:00
Zanie Blue	9b8d6989d4	Allow pinning managed Python versions to specific build versions (#15314) ... Allows pinning the Python build version via environment variables, e.g., `UV_PYTHON_CPYTHON_BUILD=...`. Each variable is implementation specific, because they use different versioning schemes. Updates the Python download metadata to include a `build` string, so we can filter downloads by the pin. Writes the build version to a file in the managed install, e.g., `cpython-3.10.18-macos-aarch64-none/BUILD`, so we can filter installed versions by the pin. Some important follow-up here: - Include the build version in not found errors (when pinned) - Automatically use a remote list of Python downloads to satisfy build versions not present in the latest embedded download metadata Some less important follow-ups to consider: - Allow using ranges for build version pins	2025-08-25 16:25:05 -05:00
Charlie Marsh	ac84f5aedc	Move preview features into a dedicated crate (#15482) ... ## Summary This is causing some cyclic dependencies issues for me, because these can be used in virtually _any_ crate (like `uv-install-wheel`), which then means that all of `uv-configuration` becomes a dependency, etc. I think this should be a leaf crate so that we can safely depend on it anywhere.	2025-08-24 09:55:30 -04:00
konsti	25bedeadea	Stop leaking strings in Python downloads (#15418) ... We should not unnecessarily leak memory. Instead, we follow the general patterns and use `Cow` for strings that can be from either a static or a dynamic source.	2025-08-21 17:54:39 +02:00
github-actions[bot]	f1a023d384	Update Pyodide to 0.28.2 (#15385) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-21 01:04:15 +00:00
github-actions[bot]	724e4c7e5e	Sync latest Python releases (#15363) ... Automated update for Python releases. --------- Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com> Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-08-18 21:49:00 +00:00
Zanie Blue	00e888098f	Skip interpreters that are not found on query (#15315) ... Closes https://github.com/astral-sh/uv/issues/12155 We already throw this error earlier if we cannot find the interpreter c318e8860e/crates/uv-python/src/interpreter.rs (L1039) Why the pyenv-win shim _exists_ but fails to run with a not found error is beyond me. I think I'll take the incremental improvement here by just ignoring it. We can try to support their shims later? #15317 confirms the fix.	2025-08-18 10:42:48 -05:00
github-actions[bot]	42beb20b90	Add Python 3.14.0rc2 (#15285) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-14 13:18:36 -05:00
github-actions[bot]	c4e5984258	Sync latest Python releases (#15266) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-14 04:28:47 +00:00
Zanie Blue	2c54d3929c	Allow selection of pyodide interpreters with "pyodide" (#15256)	2025-08-13 19:08:55 +00:00
Ahmed Ilyas	88a7b2d864	Fix clippy warnings in downloads.rs (#15255) ... ## Summary Fixes clippy warnings on main. ## Test Plan `cargo clippy`	2025-08-13 12:21:03 -05:00
Hood Chatham	c8d0bfba5c	Add support for installing pyodide Pythons (#14518) ... - [x] Add tests --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-08-13 11:03:25 -05:00
Zanie Blue	b38edb9b7d	Allow Python requests with missing segments (#14399) ... This allows `PythonDownloadRequest` which is used for parsing general install key requests to have missing segments, which unblocks requests like `windows-aarch64` or `cpython-linux` (whereas before those would require `any-any-windows-aarch64` and `cpython-any-linux` respectively). We still require strict ordering of segments. Previously, we only allowed missing segments at the end of the key. This uses a state machine for parsing, which is quite a bit more complicated. I'm a little hesitant about the possibility that this regresses error messages and the complexity of the implementation, but `uv run -p aarch64` seems valuable following #13724. The alternative to this would probably be to make these explicit in various places? e.g., expose `--python-arch`, `--python-libc`, and `--python-os`? Or make `--python-platform` (which already exists) accept a subset of the keys? There is a possibility of regressions here, e.g., if something matches this parser it will not fallback to the `PythonRequest::ExecutableName` case and we've made this parser more permissive, but I think that should be quite rare?	2025-08-13 11:03:09 -05:00
Zanie Blue	78c8c711fa	Refactor os, arch, and libc information into a shared Platform type (#15027) ... Addresses this outstanding item from a previous review https://github.com/astral-sh/uv/pull/13724#discussion_r2114867288 I'm interested in this now for consolidating some logic in #12731	2025-08-13 09:02:55 -05:00
github-actions[bot]	ed499d7453	Sync latest Python releases (#15186) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-08-09 00:43:10 +00:00
github-actions[bot]	d1beb7f640	Sync latest Python releases (#15171) ... Automated update for Python releases. This picks up dynamically-linked tkinter/libtcl/libtk, which fixes #6893 and a host of similar issues. Co-authored-by: Geoffrey Thomas <geofft@ldpreload.com>	2025-08-08 19:03:25 +00:00
Zanie Blue	bdb4b061db	Include all site packages directories in ephemeral environment overlays (#15121) ... Related to https://github.com/astral-sh/uv/issues/15113 The case in the linked issue is that we perhaps should not be allowing `uv run --with` with system interpreters at all. I think we can consider that, but the issue highlighted that `uv run --with` for a system interpreter is broken if the base interpreter has custom site packages. This generalizes beyond system interpreters so we should probably fix our overlays.	2025-08-08 13:49:21 -05:00
samypr100	57df0146e2	Update Rust toolchain to 1.89 (#15157) ... ## Summary Bumps Rust toolchain to 1.89, but not the MSRV. Lifetime changes is related to a new lint rule explained in https://blog.rust-lang.org/2025/08/07/Rust-1.89.0/#mismatched-lifetime-syntaxes-lint ## Test Plan Existing Tests	2025-08-08 13:01:52 +00:00
Michael Šimáček	e5eec05783	Ignore GraalPy devtag (#15013) ... Allows [development builds of GraalPy](https://github.com/graalvm/graal-languages-ea-builds) to work with uv. CC @timfel	2025-08-07 15:53:37 -05:00
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
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
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
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	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	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	f7ac6875c3	Improve concurrency safety of Python downloads into cache (#14846)	2025-07-23 11:52:39 -05:00
github-actions[bot]	310a9d3426	Sync latest Python releases (#14847) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-07-23 11:01:09 -05:00
Charlie Marsh	d052427c37	Accept &Path when creating executable links (#14791) ... ## Summary I don't see a great reason for this to take an owned value. It only needs an owned value for error cases.	2025-07-21 11:53:28 -04:00
Jo	9983273289	Use sha256 checksum from GitHub API for GraalPy releases (#14779) ... ## Summary Follow #14078, use GitHub generated sha256 for GraalPy releases too. ## Test Plan ```console uv run ./crates/uv-python/fetch-download-metadata.py ```	2025-07-21 08:35:45 -04:00
Jo	98d6ab6632	Improve CPythonFinder._parse_download_url a bit (#14780) ... ## Summary Rename `_parse_download_url` to `_parse_download_asset` and move the `asset['digest']` logic into it. ## Test Plan ```console uv run ./crates/uv-python/fetch-download-metadata.py ```	2025-07-21 12:22:45 +02:00
konsti	574aa1ef11	Better error reporting for removing Python versions from the Windows registry (#14722) ... See 4625800484 We didn't actual use a format string, showing the template instead. We don't show the causes in the error report, so we format it into one error.	2025-07-18 13:26:47 +00:00