6701 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Zanie Blue	62ed17b230	Bump version to 0.7.13 (#14002)	2025-06-12 14:33:31 -05:00
konsti	7316bd01a3	Build backend: Support namespace packages (#13833) ... Unlike regular packages, specifying all `__init__.py` directories for a namespace package would be very verbose There is e.g. https://github.com/python-poetry/poetry/tree/main/src/poetry, which has 18 modules, or https://github.com/googleapis/api-common-protos which is inconsistently nested. For both the Google Cloud SDK, there are both packages with a single module and those with complex structures, with many having multiple modules due to versioning through `<module>_v1` versioning. The Azure SDK seems to use one module per package (it's not explicitly documented but seems to follow from the process in https://azure.github.io/azure-sdk/python_design.html#azure-sdk-distribution-packages and ccb0e03a3d/doc/dev/packaging.md). For simplicity with complex projects, we add a `namespace = true` switch which disabled checking for an `__init__.py`. We only check that there's no `<module_root>/<module_name>/__init__.py` and otherwise add the whole `<module_root>/<module_name>` folder. This comes at the cost of `namespace = true` effectively creating an opt-out from our usual checks that allows creating an almost entirely arbitrary package. For simple projects with only a single module, the module name can be dotted to point to the target module, so the build still gets checked: ```toml [tool.uv.build-backend] module-name = "poetry.core" ``` ## Alternatives ### Declare all packages We could make `module-name` a list and allow or require declaring all packages: ```toml [tool.uv.build-backend] module-name = ["cloud_sdk.service.storage", "cloud_sdk.service.storage_v1", "cloud_sdk.billing.storage"] ``` Or for Poetry: ```toml [tool.uv.build-backend] module-name = [ "poetry.config", "poetry.console", "poetry.inspection", "poetry.installation", "poetry.json", "poetry.layouts", "poetry.masonry", "poetry.mixology", "poetry.packages", "poetry.plugins", "poetry.publishing", "poetry.puzzle", "poetry.pyproject", "poetry.repositories", "poetry.toml", "poetry.utils", "poetry.vcs", "poetry.version" ] ``` ### Support multiple namespaces We could also allow namespace packages with multiple root level module: ```toml [tool.uv.build-backend] module-name = ["cloud_sdk.my_ext", "local_sdk.my_ext"] ``` For lack of use cases, we delegate this to creating a workspace with one package per module. ## Implementation Due to the more complex options for the module name, I'm moving verification on deserialization later, dropping the source span we'd get from serde. We also don't show similarly named directories anymore. --------- Co-authored-by: Andrew Gallant <andrew@astral.sh>	2025-06-12 17:23:58 +00:00
Zanie Blue	95ad8e5e82	Add 3.14 to the supported platform reference (#13990)	2025-06-12 15:18:48 +00:00
Zanie Blue	e067118700	Add supported macOS version to the platform reference (#13993) ... Closes https://github.com/astral-sh/uv/issues/13807	2025-06-12 15:16:24 +00:00
Zanie Blue	f82909ad68	Update platform support reference to include Python implementation list (#13991)	2025-06-12 10:14:42 -05:00
github-actions[bot]	d9c34259b3	Sync latest Python releases (#13996) ... Automated update for Python releases. --------- Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com> Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-06-12 09:47:28 -05:00
Ahmed Ilyas	a1f9f28762	Do not allow uv add --group ... --script (#13997) ... ## Summary Closes #13988 ## Test Plan `cargo test`	2025-06-12 10:45:12 -04:00
Zanie Blue	806cc5cad9	Debug sync_dry_run flake by panicking with verbose output on failure (#13817) ... Investigating #13744 I tried reproducing here by running the test in a loop, but could not. I presume it's an interaction with other tests. This drops the snapshot, but I think it's worth it to try to examine the flake?	2025-06-12 08:05:25 -05:00
Zanie Blue	87ab57e902	Update the CLI help and reference to include references to the Python bin directory (#13978) ... Closes https://github.com/astral-sh/uv/issues/13977	2025-06-12 10:02:51 +00:00
konsti	b3d7f79770	Universal sync_required_environment_hint test (#13975) ... Use the packse case `no-sdist-no-wheels-with-matching-platform` for a platform independent `sync_required_environment_hint` test. Fixes #13890	2025-06-11 22:47:40 -04:00
Charlie Marsh	81aebf921d	Add zstd and deflate to Accept-Encoding (#13982) ... ## Summary We already pull in these dependencies, so it costs us nothing.	2025-06-11 22:42:47 -04:00
Zanie Blue	f530565323	Use TTY detection to determine if SIGINT forwarding is enabled (#13925) ... Use TTY detection to determine when we should forward SIGINT instead of counting signals, which can lead to various problems where multiple SIGINTs are sent to a child after the first signal. Counting does not make sense in interactive situations that do not exit on interrupt, e.g., the Python REPL. Closes https://github.com/astral-sh/uv/issues/13919 Closes https://github.com/astral-sh/uv/issues/12108	2025-06-11 13:28:34 +00:00
github-actions[bot]	357fc91c3c	Sync latest Python releases (#13956) ... Automated update for Python releases. Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>	2025-06-10 21:13:32 -05:00
Zanie Blue	4c877b7dc6	Fix generated file change (#13957) ... Regressed in https://github.com/astral-sh/uv/pull/13620 ref failure at 4384658790	2025-06-10 22:03:01 +00:00
Zanie Blue	21986c3fc9	Bump timeout on Python download release fetch (#13955) ... Failing with a 504 at 1556959077 Successful at 4384626025	2025-06-10 16:54:42 -05:00
Lan, Jian	90a7208a73	Fix and improve docs (#13620) ... <!-- 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 follow the advices from the IDE spell checker and grammar checker, fix some typos, and improve the docs.	2025-06-10 13:15:38 -05:00
Zanie Blue	f20a25f91f	Download versions in uv python pin if not found (#13946) ... As another follow-up in the vein of https://github.com/astral-sh/uv/pull/13944, I noticed `uv python pin` doesn't download Python versions, which is a bit weird because we'll warn it's not found.	2025-06-10 10:56:22 -05:00
Xeonacid	210b579188	build-binaries for riscv64 (#12688) ... <!-- 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? --> Build riscv64 binary so it can get released in the GitHub Releases, which is used by many high-level apps. A copy-paste from linux-s390x, with only target and arch changed. maturin-action added riscv64 support in v1.48.0, this PR also bumps it to the latest version, v1.48.1. ## Test Plan <!-- How was it tested? --> Let CI test itself :P Already tested in [my fork](4004817230)	2025-06-10 11:18:28 -04:00
Zanie Blue	1b82a3ac99	Ignore Python discovery errors during uv python pin (#13944) ... See https://github.com/astral-sh/uv/issues/13935#issuecomment-2957300516 where we fail to write a pin file because we encounter an unusable interpreter. This is actually a special case where `MissingPython` is not raised because we want to show why we failed to find a usable interpreter, which is useful in commands where you _need_ an interpreter to use, but here we don't actually need it. Here, we just log the failure and move on. Related https://github.com/astral-sh/uv/pull/13936	2025-06-10 09:52:23 -05:00
Charlie Marsh	28685633c0	Add an llms.txt to uv (#13929) ... ## Summary The generated file looks like: ``` # uv > uv is an extremely fast Python package and project manager, written in Rust. You can use uv to install Python dependencies, run scripts, manage virtual environments, build and publish packages, and even install Python itself. uv is capable of replacing `pip`, `pip-tools`, `pipx`, `poetry`, `pyenv`, `twine`, `virtualenv`, and more. uv includes both a pip-compatible CLI (prepend `uv` to a pip command, e.g., `uv pip install ruff`) and a first-class project interface (e.g., `uv add ruff`) complete with lockfiles and workspace support. ## Getting started - [Features](https://docs.astral.sh/uv/getting-started/features/index.md) - [First steps](https://docs.astral.sh/uv/getting-started/first-steps/index.md) - [Installation](https://docs.astral.sh/uv/getting-started/installation/index.md) ## Guides - [Installing Python](https://docs.astral.sh/uv/guides/install-python/index.md) - [Publishing packages](https://docs.astral.sh/uv/guides/package/index.md) - [Working on projects](https://docs.astral.sh/uv/guides/projects/index.md) - [Running scripts](https://docs.astral.sh/uv/guides/scripts/index.md) - [Using tools](https://docs.astral.sh/uv/guides/tools/index.md) ## Integrations - [Alternative indexes](https://docs.astral.sh/uv/guides/integration/alternative-indexes/index.md) - [AWS Lambda](https://docs.astral.sh/uv/guides/integration/aws-lambda/index.md) - [Dependency bots](https://docs.astral.sh/uv/guides/integration/dependency-bots/index.md) - [Docker](https://docs.astral.sh/uv/guides/integration/docker/index.md) - [FastAPI](https://docs.astral.sh/uv/guides/integration/fastapi/index.md) - [GitHub Actions](https://docs.astral.sh/uv/guides/integration/github/index.md) - [GitLab CI/CD](https://docs.astral.sh/uv/guides/integration/gitlab/index.md) - [Jupyter](https://docs.astral.sh/uv/guides/integration/jupyter/index.md) - [marimo](https://docs.astral.sh/uv/guides/integration/marimo/index.md) - [Pre-commit](https://docs.astral.sh/uv/guides/integration/pre-commit/index.md) - [PyTorch](https://docs.astral.sh/uv/guides/integration/pytorch/index.md) ## Projects - [Building distributions](https://docs.astral.sh/uv/concepts/projects/build/index.md) - [Configuring projects](https://docs.astral.sh/uv/concepts/projects/config/index.md) - [Managing dependencies](https://docs.astral.sh/uv/concepts/projects/dependencies/index.md) - [Creating projects](https://docs.astral.sh/uv/concepts/projects/init/index.md) - [Structure and files](https://docs.astral.sh/uv/concepts/projects/layout/index.md) - [Running commands](https://docs.astral.sh/uv/concepts/projects/run/index.md) - [Locking and syncing](https://docs.astral.sh/uv/concepts/projects/sync/index.md) - [Using workspaces](https://docs.astral.sh/uv/concepts/projects/workspaces/index.md) ## Features - [Authentication](https://docs.astral.sh/uv/concepts/authentication/index.md) - [Build backend](https://docs.astral.sh/uv/concepts/build-backend/index.md) - [Caching](https://docs.astral.sh/uv/concepts/cache/index.md) - [Configuration files](https://docs.astral.sh/uv/concepts/configuration-files/index.md) - [Package indexes](https://docs.astral.sh/uv/concepts/indexes/index.md) - [Python versions](https://docs.astral.sh/uv/concepts/python-versions/index.md) - [Resolution](https://docs.astral.sh/uv/concepts/resolution/index.md) - [Tools](https://docs.astral.sh/uv/concepts/tools/index.md) ## The pip interface - [Compatibility with pip](https://docs.astral.sh/uv/pip/compatibility/index.md) - [Locking environments](https://docs.astral.sh/uv/pip/compile/index.md) - [Declaring dependencies](https://docs.astral.sh/uv/pip/dependencies/index.md) - [Using environments](https://docs.astral.sh/uv/pip/environments/index.md) - [Inspecting environments](https://docs.astral.sh/uv/pip/inspection/index.md) - [Managing packages](https://docs.astral.sh/uv/pip/packages/index.md) ## Reference - [Commands](https://docs.astral.sh/uv/reference/cli/index.md) - [Environment variables](https://docs.astral.sh/uv/reference/environment/index.md) - [Installer](https://docs.astral.sh/uv/reference/installer/index.md) - [Settings](https://docs.astral.sh/uv/reference/settings/index.md) ``` Closes #13901.	2025-06-10 07:46:49 -04:00
konsti	c54f131500	Add basic network error tests (#13585) ... Add basic tests for error messages on retryable network errors. This test mod is intended to grow to ensure that we handle retryable errors correctly and that we show the appropriate error message if we failed after retrying. The starter tests show some common cases we've seen download errors in: simple and find links indexes, file downloads and Python installs. For `io::Error` fault injection to test the reqwest `Err` path besides the HTTP status code `Ok` path, see https://github.com/LukeMathWalker/wiremock-rs/issues/149.	2025-06-10 12:00:04 +02:00
Jack O'Connor	9129d2a9a3	avoid fetching an exact, cached commit, even if it isn't locked ... Fixes #13513 and #12746.	2025-06-09 23:50:36 +00:00
Jack O'Connor	619132bd8a	make GitOid strict about parsing exactly 40 hex characters	2025-06-09 23:50:36 +00:00
Jack O'Connor	9ff07c113f	add a snapshot test for uv pip install with an exact Git commit	2025-06-09 23:50:36 +00:00
Jack O'Connor	dc455bfc26	add UV_NO_GITHUB_FAST_PATH	2025-06-09 23:50:36 +00:00
renovate[bot]	f5382c010b	Update acj/freebsd-firecracker-action action to v0.4.2 (#13906) ... This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [acj/freebsd-firecracker-action](https://redirect.github.com/acj/freebsd-firecracker-action) | action | patch | `v0.4.1` -> `v0.4.2` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>acj/freebsd-firecracker-action (acj/freebsd-firecracker-action)</summary> ### [`v0.4.2`](https://redirect.github.com/acj/freebsd-firecracker-action/releases/tag/v0.4.2) [Compare Source](https://redirect.github.com/acj/freebsd-firecracker-action/compare/v0.4.1...v0.4.2) [Firecracker 1.12.0](https://redirect.github.com/firecracker-microvm/firecracker/releases/tag/v1.12.0) [FreeBSD 14.3-RELEASE](https://www.freebsd.org/releases/14.3R/relnotes/) </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:eyJjcmVhdGVkSW5WZXIiOiI0MC40MC4zIiwidXBkYXRlZEluVmVyIjoiNDAuNDAuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiaW50ZXJuYWwiXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-06-09 18:06:31 -05:00
renovate[bot]	e67dff85cc	Update Rust crate fs-err to v3.1.1 (#13910)	2025-06-09 14:29:12 -04:00
renovate[bot]	dd46985e27	Update Rust crate petgraph to v0.8.2 (#13913)	2025-06-09 14:28:51 -04:00
renovate[bot]	2940122e69	Update Rust crate hashbrown to v0.15.4 (#13911)	2025-06-09 14:28:39 -04:00
renovate[bot]	1f2bba9b3d	Update Rust crate flate2 to v1.1.2 (#13909)	2025-06-09 14:28:26 -04:00
renovate[bot]	64dacab913	Update pre-commit dependencies (#13907)	2025-06-09 14:28:16 -04:00
renovate[bot]	00b517dbd1	Update Rust crate anstream to v0.6.19 (#13908)	2025-06-09 14:28:09 -04:00
John Mumm	2a66349e96	Check if relative URL is valid directory before treating as index (#13917) ... As per #13874, passing a relative URL like `test` to `--index` for `uv add` causes unexpected behavior if the directory does not exist. The non-existent index is effectively ignored and uv falls back to PyPI. If a package is found there, the spurious index is then written to `pyproject.toml`. This doesn't happen for `--default-index` since resolution will fail without fallback to PyPI. This PR adds a validation step for indexes provided on the command line. If a directory does not exist, uv will fail with an error. Closes #13874	2025-06-09 19:28:39 +02:00
Zanie Blue	619a0eafa1	Fix use of deprecated black_box function (#13926)	2025-06-09 16:57:27 +00:00
Zanie Blue	ea45acaf4f	Fix extra newline in changelog (#13918)	2025-06-09 11:48:59 -05:00
Karim Abou Zeid	5dae9ac5f2	Update referenced CUDA version in pytorch.md (#13899) ... ## Summary torch 2.7 by default targets CUDA 12.6	2025-06-08 20:21:07 -04:00
Zanie Blue	dc3fd46472	Bump version to 0.7.12 (#13892)	2025-06-06 19:42:06 +00:00
konsti	5b0133c0ec	Hint at tool.uv.required-environments (#13575) ... For the case where there was no matching wheel on sync, we previously added a note about which wheels are available vs. on which platform you are on. We extend this error message to link directly towards `tool.uv.required-environments`, which otherwise has a discovery problem. On Linux (Setting `tool.uv.required-environments` doesn't help here either, but it's a clear example): ``` [project] name = "debug" version = "0.1.0" requires-python = "==3.10.*" dependencies = ["tensorflow-macos>=2.13.1"] ``` ``` Resolved 41 packages in 24ms error: Distribution `tensorflow-macos==2.16.2 @ registry+https://pypi.org/simple` can't be installed because it doesn't have a source distribution or wheel for the current platform hint: You're on Linux (`manylinux_2_39_x86_64`), but there are no wheels for the current platform, consider configuring `tool.uv.required-environments`. hint: `tensorflow-macos` (v2.16.2) only has wheels for the following platform: `macosx_12_0_arm64`. ```  --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-06-06 19:15:52 +00:00
konsti	7aefbe8dc5	Don't hint at versions removed by excluded-newer (#13884) ... General small hint false positives that shows up as CI failure in our snapshots. Fixes #13867	2025-06-06 18:35:18 +00:00
konsti	0109af1aa5	Hint at tool.uv.environments on resolution error (#13455) ... Users are not (yet) properly familiar with the concept of universal resolution and its implication that we need to resolve for all possible platforms and Python versions. Some projects only target a specific platform or Python version, and users experience resolution errors due to failures for other platforms. Indicated by the number of questions we get about it, `tool.uv.environments` for restricting environments is not well discoverable. We add a special hint when resolution failed on a fork disjoint with the current environment, hinting the user to constrain `requires-python` and `tool.uv.environments` respectively. The hint has false positives for cases where the resolution failed on a different platform, but equally fails on the current platform, in cases where the non-current fork was tried earlier. Given that conflicts can be based on `requires-python`, afaik we can't parse whether the current platform would also be affected from the derivation tree. Two cases not covered by this are build errors as well as install errors that need `tool.uv.required-environments`.	2025-06-06 14:17:52 +00:00
Yury Fedotov	8a88ab2c70	Minor internal README enhancement for Markdown list in PEP440 (#13880) ... - Define all list elements using `-`: it used to be a mix of `*` and `-`. `-` is what Prettier linter formats it to by default. - Removed unnecessary blank line between 2 list elements. Other elements were stitched together without blank lines in between. - Only the first list element started in sentence case (capital letter first) - I made all start like so.	2025-06-06 08:45:37 -05:00
konsti	bf96c60e3e	Lock during uv sync, uv add and uv remove to avoid race conditions (#13869) ... Surprisingly, we weren't locking during `uv sync` so far, so running `uv sync` in parallel could cause errors in filesystem races. I've also added locks to `uv add` and `uv remove` which concurrently modify `pyproject.toml`. These locks only apply after we determined the interpreter, so they don't actually prevent computing the same thing twice when running `uv add` in parallel. All other subcommands that I checked were already locking (with no claim to exhaustiveness) Fixes #12751 # Test Plan I don't have CI-sized reproducer for this. ```toml [project] name = "debug" version = "0.1.0" requires-python = ">=3.12" dependencies = [ "boto3>=1.38.30", "fastapi>=0.115.12", "numba>=0.61.2", "polars>=1.30.0", "protobuf>=6.31.1", "pyarrow>=20.0.0", "pydantic>=2.11.5", "requests>=2.32.3", "urllib3>=2.4.0", "scikit-learn>=1.6.1", "jupyter>=1.1.1", ] [build-system] requires = ["hatchling"] build-backend = "hatchling.build" ``` ``` rm -rf .venv && parallel -n0 "uv sync -q" ::: {1..10} ```	2025-06-06 14:16:40 +02:00
Micha Reiser	b865f76b78	Change GlobDirFilter fallback to true (#13882) ... ## Summary I think `GlobDirFilter::match_directory` should return `true` if it failed to construct a DFA to force a full directory traversal. Returning `false` means that the build backend excludes all files which is unlikely what we want in that situation.	2025-06-06 14:07:34 +02:00
samypr100	a68fb53c4b	PEP 751 uv export supports --no-editable (#13852) ... ## Summary When trying out `uv export --no-editable --format pylock.toml` the exported contents would still retain `editable = true` regardless. ## Test Plan Added additional test. Tested locally on few projects where I was previously using `uv export --no-editable --format requirements.txt` to ensure the output aligns.	2025-06-06 07:52:14 -04:00
Zanie Blue	7dd564d3d0	Improve python pin error messages (#13862) ... Addresses https://github.com/astral-sh/uv/issues/13854	2025-06-05 21:48:34 +00:00
Jack O'Connor	94ed6f880f	update Git and GitHub Actions docs to mention gh auth login (#13850)	2025-06-05 20:44:59 +00:00
Zanie Blue	b1a50c33cf	Fix lock_requires_python test case (#13866) ... Tracking https://github.com/astral-sh/uv/issues/13867	2025-06-05 17:27:52 +00:00
Zanie Blue	262ca73965	Remove the configuration section in favor of concepts / reference (#13842) ... Extends https://github.com/astral-sh/uv/pull/13841 — I'll drop that commit later after that pull request merges but it's small. I find the split into a "Configuration" section awkward and don't think it's helping us. Everything moved into the "Concepts" section, except the "Environment variables" page which definitely belongs in the reference and the "Installer" page which is fairly niche and seems better in the reference. Before / After <img src="https://github.com/user-attachments/assets/80d8304b-17da-4900-a5f4-c3ccac96fcc5" width="400">	2025-06-05 17:09:49 +00:00
Zanie Blue	062b6ab743	Add uv python pin --rm to remove .python-version pins (#13860) ... I realized it is non-trivial to delete the global Python version pin, and that we were missing this simple functionality	2025-06-05 12:05:42 -05:00
Zanie Blue	789a246cf3	Move the pip interface documentation into the concepts section (#13841) ... The motivation here being a reduction in the length of the navigation. I don't think we did this in the first place because we didn't have the capability to do another nested level, but now we're doing that for Projects.	2025-06-05 11:53:27 -05:00