320 commits

Author	SHA1	Message	Date
11happy	1bb547b6d4	feat: implement --force flag for lock ... Signed-off-by: 11happy <soni5happy@gmail.com>	2025-09-29 22:59:33 +05:30
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	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	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
Charlie Marsh	422863ffde	Infer check URL from publish URL when known (#15886) ... ## Summary If we know the publish URL-to-check URL mapping, we can just infer it.	2025-09-16 14:03:03 +00:00
Harsh Pratap Singh	5f2871e695	Support Gitlab CI/CD as a trusted publisher (#15583) ... Co-authored-by: William Woodruff <william@astral.sh>	2025-09-11 10:35:04 -04:00
Yiğit Ö. Ünver	19ea0f4932	support --no-project in uv format (#15572) ... When a user passes `--no-project` argument to `uv format` command, instead of running the formatter in the context of the current project, run it in the context of the current directory. This is useful when the current directory is not a project. Closes https://github.com/astral-sh/uv/issues/15462	2025-09-08 16:16:40 -05:00
Zanie Blue	5f8c7181b9	Improve the CLI help for options that accept requirements files (#15706)	2025-09-08 08:23:52 -05:00
Ahmed Ilyas	6eefde28e7	Support --with-requirements script.py and -r script.py to include inline dependency metadata from another script (#12763) ... ## Summary Closes #6542 ## Test Plan `cargo test`	2025-09-05 11:45:46 -05:00
timrid	330e56e778	Support iOS platform tags (#15640) ... ## Summary This implements the iOS part of https://github.com/astral-sh/uv/issues/8029 FYI: @freakboy3742 <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan Create a venv with uv and run `cargo run pip install --python-platform arm64-apple-ios pillow`. Then the iOS binary of pillow should be installed inside the venv.	2025-09-03 18:24:48 -04:00
timrid	d178e45368	Support Android platform tags (#15646) ... ## Summary This implements the Android part of https://github.com/astral-sh/uv/issues/8029 FYI: @freakboy3742 @mhsmith <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan Create a venv with uv and run `cargo run pip install --python-platform aarch64-linux-android pybase64`. Then the Android binary of pybase64 should be installed inside the venv.	2025-09-03 10:24:33 -04:00
konsti	a94f7d0847	Clarify that uv auth commands take a URL (#15664) ... From the previous description I tried `uv auth token pyx`, which didn't work. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-03 14:16:16 +00:00
Charlie Marsh	ad35d120d6	Make uv auth dir service-aware (#15649) ... ## Summary This got lost when https://github.com/astral-sh/uv/pull/15637 was merged into not-`main`.	2025-09-02 22:58:59 -04:00
Charlie Marsh	7606f1ad3c	Add uv publish --dry-run (#15638) ... ## Summary `uv publish --dry-run` will perform the `--check-url` validation, and hit the `/validate` endpoint if the registry is known to support fast-path validation (like pyx). The `/validate` endpoint lets us validate an upload without uploading the file _contents_, which lets you skip the expensive step for common mistakes. In the future, my hope is that the `/validate` step will deprecated in favor of Upload API 2.0.	2025-09-02 21:24:31 -04:00
Zanie Blue	f9e98d1fb6	Allow providing the uv auth login password or token via stdin (#15642)	2025-09-02 16:59:58 -05:00
Zanie Blue	709e0ba238	Remove the native system store from the keyring providers (#15612) ... We're not sure what the best way to expose the native store to users is yet and it's a bit weird that you can use this in the `uv auth` commands but can't use any of the other keyring provider options. The simplest path forward is to just not expose it to users as a keyring provider, and instead frame it as a preview alternative to the plaintext uv credentials store. We can revisit the best way to expose configuration before stabilization. Note this pull request retains the _internal_ keyring provider implementation — we can refactor it out later but I wanted to avoid a bunch of churn here.	2025-09-02 13:16:52 -05:00
Zanie Blue	7d627b50ef	Add uv auth dir (#15600)	2025-09-02 13:16:52 -05:00
Charlie Marsh	7d9446450b	Misc. tweaks	2025-09-02 13:16:52 -05:00
Zanie Blue	460ea6e9eb	Add uv auth commands (login, logout, and token) (#15539) ... Picks up the work from - #14559 - https://github.com/astral-sh/uv/pull/14896 There are some high-level changes from those pull requests 1. We do not stash seen credentials in the keyring automatically 2. We use `auth login` and `auth logout` (for future consistency) 3. We add a `token` command for showing the credential that will be used As well as many smaller changes to API, messaging, testing, etc. --------- Co-authored-by: John Mumm <jtfmumm@gmail.com>	2025-09-02 13:16:52 -05:00
Jo Shields	f76e0fe5e6	Add --python-platform riscv64-unknown-linux to various commands (#15630) ... ## Summary We (and I'm sure many others) are currently doing a lot of RISC-V work in QEMU. It is possible to significantly improve the speed of Python-related builds by taking care of the environment setup using an AMD64 `uv` binary (bypassing binfmt/qemu-system emulation). Some approx numbers from local testing in riscv64 Ubuntu in QEMU: | Resolver arch | Command | Time | | --- | --- | --- | | riscv64 | `pip install --upgrade --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 15s | | riscv64 | `uv pip install --upgrade --system --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 5s | | amd64 | `uv pip install --python-platform=riscv64-unknown-linux --upgrade --system --break-system-packages --index-url=https://gitlab.com/api/v4/projects/riseproject%2Fpython%2Fwheel_builder/packages/pypi/simple openai-harmony` | 4s | The numbers from some larger internal packages with deeper dependency trees are much more pronounced - 3m6 vs 43s vs 8s, in one example. Manylinux 2.39 is specified, as it's the first (only?) RISC-V manylinux ## Test Plan Locally, in QEMU. `$ docker run --platform linux/riscv64 -it ubuntu:latest`, get amd64 libc into LD_LIBRARY_PATH, tests as above	2025-09-02 13:17:30 -04:00
Harsh Pratap Singh	d877899920	Add uv tree --show-sizes to show package sizes (#15531) ... <!-- 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 Adds the enhancement proposed in #15470. Each package in the dependency tree now shows its compressed wheel file size, reading the wheel sizes directly from the lockfile (uv.lock). Doesn't break existing tree formatting or options. If no wheel size is available, nothing is added. Now, developers can identify large packages in their dependency tree. The tree still shows extras exactly as before, and then appends a size for the package. ## Test Plan Manually tested : ``` harsh@fcr-node:~/uv/test-uv-tree-sizes$ ../target/debug/uv tree Using CPython 3.13.7 warning: No `requires-python` value found in the workspace. Defaulting to `>=3.13`. Resolved 4 packages in 6ms pure-python v0.1.0 ├── click v8.2.1 └── six v1.17.0 harsh@fcr-node:~/uv/test-uv-tree-sizes$ ../target/debug/uv tree --show-sizes Using CPython 3.13.7 warning: No `requires-python` value found in the workspace. Defaulting to `>=3.13`. Resolved 4 packages in 6ms pure-python v0.1.0 ├── click v8.2.1 (99.8KiB) └── six v1.17.0 (10.8KiB) ```	2025-08-29 08:31:46 -05:00
Charlie Marsh	4168d9b320	Add --python-platform to uv run and uv tool (#15515) ... ## Summary Closes https://github.com/astral-sh/uv/issues/11120.	2025-08-29 00:51:39 +00:00
Charlie Marsh	d19d0e26aa	Add --python-platform to uv pip check (#15486) ... ## Summary I want this to facilitate some testing for https://github.com/astral-sh/uv/issues/15035.	2025-08-24 14:14:42 -04:00
Xavi Simpson	6e2fbbc30f	Add --no-install-local option to uv sync, uv add and uv export (#15328) ... <!-- 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? --> Closes #14866. Adds a `no-install-local` flag to the sync and export commands that excludes locally defined packages from being installed. This helps with if you're caching your virtual environment. You can exclude local packages since they're more likely to change between builds. ## Test Plan snapshot test: `sync::no_install_local` CI ## Notes I made an `InstallOptions` struct to avoid a crate isolation issue I was running into while implementing. Thanks for maintaining this project!	2025-08-22 11:31:52 -05:00
Charlie Marsh	d1e0c26678	Add an environment variable for UV_ISOLATED (#15428) ... Closes https://github.com/astral-sh/uv/issues/15427.	2025-08-21 23:39:04 +01:00
Zanie Blue	f210db0907	Fix format doc mistake (#15433)	2025-08-21 21:12:06 +00:00
youkaichao	b950453891	Add CUDA 12.9 backend (#15416) ... ## Summary Add torch cuda 12.9 backend <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan <!-- How was it tested? --> --------- Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-08-21 16:01:02 +01:00
Zanie Blue	e31f000da7	Add an experimental uv format command (#15017) ... As a frontend to Ruff's formatter. There are some interesting choices here, some of which may just be temporary: 1. We pin a default version of Ruff, so `uv format` is stable for a given uv version 2. We install Ruff from GitHub instead of PyPI, which means we don't need a Python interpreter or environment 3. We do not read the Ruff version from the dependency tree See https://github.com/astral-sh/ruff/pull/19665 for a prototype of the LSP integration.	2025-08-21 06:33:18 -05:00
Charlie Marsh	68f33e8fef	Add --no-install-* arguments to uv add (#15375) ... ## Summary Closes https://github.com/astral-sh/uv/issues/15369.	2025-08-19 15:32:56 +01:00
Zanie Blue	242214c546	Add an aarch64-pc-windows-msvc target (#15347) ... I needed this and was surprised it didn't exist! --------- Co-authored-by: konsti <konstin@mailbox.org>	2025-08-18 17:57:27 +00:00
NewDestinyDan	191c9175fe	Update cli.md to use proper uv cache subcommand "clean" (#15313) ... Correct typo. "uv cache clear" is not a command. <!-- 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? --> ## Test Plan <!-- How was it tested? -->	2025-08-15 21:06:37 +00:00
John Mumm	23245c63e9	Add --reinstall flag to uv python upgrade (#15194) ... As described in #15179, there are cases where it can be useful to reinstall the latest patch on upgrade if it is already installed. Using this flag, you don't need to know ahead of time if you have the latest patch already. Closes #15179.	2025-08-11 15:20:04 -05:00
Charlie Marsh	f6a9b55eb7	Add UV_DEV and UV_NO_DEV environment variables (#15010) ... ## Summary Closes https://github.com/astral-sh/uv/issues/15009. Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-08-08 14:33:44 +00:00
konsti	84d57f2ee9	Ensure symlink warning is shown (#15126) ... Fixes #15115, see also https://github.com/clap-rs/clap/discussions/6092 <img width="1079" height="1030" alt="image" src="https://github.com/user-attachments/assets/05b003a6-9ca0-4f2b-8a74-078aa155ce6d" />	2025-08-07 15:56:59 +02:00
konsti	52771476f4	Support UV_NO_EDITABLE where --no-editable is supported (#15107) ... Specifically, support `UV_NO_EDITABLE=1 uv export`. It's now also supported in `uv add`, though it's default there anyway and the env var exists only for completeness. Fixes #15103	2025-08-06 13:06:49 +00: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	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	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
Zanie Blue	396e198081	Update documentation for preview flags (#14902) ... Follows #14823	2025-07-25 15:19:24 -05:00
Zanie Blue	8289e38e8f	Add UV_INIT_BUILD_BACKEND (#14821) ... Closes https://github.com/astral-sh/uv/issues/14820	2025-07-22 14:10:08 -05:00
Charlie Marsh	b81cce9152	Support extras and dependency_groups markers on uv pip install and uv pip sync (#14755) ... ## Summary We don't yet support writing these, but we can at least read them (which, e.g., allows you to install PDM-exported `pylock.toml` files with uv, since PDM _always_ writes a default group). Closes #14740.	2025-07-21 12:48:47 +00:00
Charlie Marsh	e724ddc63f	Allow --config-settings-package to apply configuration settings at the package level (#14573) ... ## Summary Closes https://github.com/astral-sh/uv/issues/14564. Closes https://github.com/astral-sh/uv/issues/10940.	2025-07-17 21:27:54 -04:00
Zanie Blue	0077f2357f	Stabilize addition of Python executables to the bin (#14626) ... Closes https://github.com/astral-sh/uv/issues/14296 As mentioned in #14681, this does not stabilize the `--default` behavior.	2025-07-17 17:20:21 -05:00
John Mumm	2df06ebfbc	Require uv venv --clear before removing an existing directory (#14309) ... By default, `uv venv <venv-name>` currently removes the `<venv-name`> directory if it exists. This can be surprising behavior: not everyone expects an existing environment to be overwritten. This PR updates the default to fail if a non-empty `<venv-name>` directory already exists and neither `--allow-existing` nor the new `-c/--clear` option is provided (if a TTY is detected, it prompts first). If it's not a TTY, then uv will only warn and not fail for now — we'll make this an error in the future. I've also added a corresponding `UV_VENV_CLEAR` env var. I've chosen to use `--clear` instead of `--force` for this option because it is used by the `venv` module and `virtualenv` and will be familiar to users. I also think its meaning is clearer in this context than `--force` (which could plausibly mean force overwrite just the virtual environment files, which is what our current `--allow-existing` option does). Closes #1472. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-07-17 17:20:21 -05:00
Charlie Marsh	c3d7d3899c	Default to --workspace when adding subdirectories (#14529) ... If `--workspace` is provided, we add all paths as workspace members. If `--no-workspace` is provided, we add all paths as direct path dependencies. If neither is provided, then we add any paths that are under the workspace root as workspace members, and the rest as direct path dependencies. Closes #14524.	2025-07-17 17:20:21 -05:00
Charlie Marsh	e4c04af32d	Bump --python-platform linux to manylinux_2_28 (#14300) ... Right now, `--python-platform linux` to defaults to `manylinux_2_17`. Defaulting to `manylinux_2_17` causes some problems for users, since it means we can't use (e.g.) `manylinux_2_28` wheels, and end up having to build from source. cibuildwheel made `manylinux_2_28` their default in https://github.com/pypa/cibuildwheel/pull/1988, and there's a lot of discussion in https://github.com/pypa/cibuildwheel/issues/1772 and https://github.com/pypa/cibuildwheel/issues/2047. In short, the `manylinux_2014` image is EOL, and the vast majority of consumers now run at least glibc 2.28 (https://mayeut.github.io/manylinux-timeline/):  Note that this only changes the _default_. Users can still compile against `manylinux_2_17` by specifying it.	2025-07-17 17:20:21 -05:00
Zanie Blue	868ecd7b3a	Add support for toggling Python bin and registry install options via env vars (#14662) ... Adds environment variables for https://github.com/astral-sh/uv/pull/14612 and https://github.com/astral-sh/uv/pull/14614 We can't use the Clap `BoolishValueParser` here, and the reasoning is a little hard to explain. If we used `UV_PYTHON_INSTALL_NO_BIN`, as is our typical pattern, it'd work, but here we allow opt-in to hard errors with `UV_PYTHON_INSTALL_BIN=1` and I don't think we should have both `UV_PYTHON_INSTALL_BIN` and `UV_PYTHON_INSTALL_NO_BIN`. Consequently, this pull request introduces a new `EnvironmentOptions` abstraction which allows us to express semantics that Clap cannot — which we probably want anyway because we have an increasing number of environment variables we're parsing downstream, e.g., #14544 and #14369.	2025-07-17 12:33:43 -05:00
Zanie Blue	d525720266	Add uv python update-shell (#14627) ... Part of #14296 This is the same as `uv tool update-shell` but handles the case where the Python bin directory is configured to a different path. ``` ❯ UV_PYTHON_BIN_DIR=/tmp/foo cargo run -q -- python install --preview 3.13.3 Installed Python 3.13.3 in 1.75s + cpython-3.13.3-macos-aarch64-none warning: `/tmp/foo` is not on your PATH. To use installed Python executables, run `export PATH="/tmp/foo:$PATH"` or `uv python update-shell`. ❯ UV_PYTHON_BIN_DIR=/tmp/foo cargo run -q -- python update-shell Created configuration file: /Users/zb/.zshenv Restart your shell to apply changes ❯ cat /Users/zb/.zshenv # uv export PATH="/tmp/foo:$PATH" ❯ UV_TOOL_BIN_DIR=/tmp/bar cargo run -q -- tool update-shell Updated configuration file: /Users/zb/.zshenv Restart your shell to apply changes ❯ cat /Users/zb/.zshenv # uv export PATH="/tmp/foo:$PATH" # uv export PATH="/tmp/bar:$PATH" ```	2025-07-15 13:47:02 -05:00
Zanie Blue	d2c81e503f	Make preview Python registration on Windows non-fatal (#14614) ... Same as #14612 for registration with the Windows Registry.	2025-07-15 17:29:11 +00:00
Zanie Blue	bb1e9a247c	Update preview installation of Python executables to be non-fatal (#14612) ... Previously, if installation of executables into the bin directory failed we'd with a non-zero code. However, if we make this behavior the default we don't want it to be fatal. There's a `--bin` opt-in to _require_ successful executable installation and a `--no-bin` opt-out to silence the warning / opt-out of installation entirely. Part of https://github.com/astral-sh/uv/issues/14296 — we need this before we can stabilize the behavior. In #14614 we do the same for writing entries to the Windows registry.	2025-07-15 17:12:36 +00:00