306 commits

Author	SHA1	Message	Date
Mikayla Thompson	f22af0f88a	Deprecate --project arg for init (#16674) ... Addresses https://github.com/astral-sh/uv/issues/15790 ## Summary After discussion, the functionality of `--project` vs `--directory` was quite unclear in this case, so deprecating `--project` for `init` is probably the clearest behavior option. This is a breaking change, so it requires being under preview before being rolled out fully. Included in the PR now: - new feature flag (`init --project` is deprecated if `--preview` or `--preview-features deprecate-project-for-init` are provided) - tests (for `--directory` behavior, as well as the current warning and future error) - documentation updated in docs/concepts/projects/init.md --------- Signed-off-by: Mikayla Thompson <mrt@mikayla.codes>	2025-11-10 16:33:08 -07:00
Zanie Blue	85c5d32284	Bump version to 0.9.8 (#16636)	2025-11-07 11:45:22 -06:00
Zanie Blue	0adb444806	Bump version to 0.9.7 (#16524)	2025-10-30 16:47:51 -05:00
Zanie Blue	2652244655	Bump version to 0.9.6 (#16500) ... Signed-off-by: William Woodruff <william@astral.sh> Co-authored-by: William Woodruff <william@astral.sh>	2025-10-29 14:08:49 -05:00
Matthijs Kok	659b4873b6	Update docs for maturin build backend init template (#16469) ... I forgot to update the docs in https://github.com/astral-sh/uv/pull/16449 Sorry!	2025-10-27 11:35:39 +01:00
Brian Dentino	ce7808d0cb	Update docs to reflect new signal forwarding semantics (#16430) ... <!-- 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? --> I am a new uv user and I was reading the docs to better understand the project scope & best practices. The section on [signal forwarding](https://docs.astral.sh/uv/concepts/projects/run/#signal-handling) with `uv run` caught my eye because I've used tools that use SIGHUP to trigger config reloads or SIGUSR1/2 to enable debugging/profiling/etc so I was a little concerned about using a runner that might block those signals. After some searching in issues/PRs, I found that this behavior was actually [changed earlier this year](https://github.com/astral-sh/uv/pull/13017) to forward additional signals (awesome!) and thought I would update the docs and save the next person/llm from thinking their tool won't work as expected if it uses custom signal handling. Thanks for all your great work! P.S. If you think it makes more sense to explicitly list all forwarded signals as opposed to just the exclusions, I'm happy to edit.	2025-10-24 14:52:08 -05:00
William Woodruff	d5f39331a7	Bump version to 0.9.5 (#16389)	2025-10-21 12:14:22 -04:00
konsti	38412a675e	Remove outdated aarch64 musl note (#16385) ... We now build aarch64 musl Python distributions. I've also removed the rye mention since it's now officially deprecated.	2025-10-21 16:08:37 +02:00
Zanie Blue	ee2649feaa	Bump version to 0.9.4 (#16347)	2025-10-17 16:02:02 -05:00
Zanie Blue	9db7d38cf7	Bump version to 0.9.3 (#16305)	2025-10-14 18:19:49 -05:00
William Woodruff	141369ce73	Bump version to 0.9.2 (#16238) ... Co-authored-by: Geoffrey Thomas <geofft@ldpreload.com>	2025-10-10 14:20:14 -04:00
Zanie Blue	9887ef5bd7	Bump version to 0.9.1 (#16212) ... Archives the 0.8.x changelog too.	2025-10-09 18:28:59 +00:00
Zanie Blue	39b6886536	Bump version to 0.9.0 (#16161) ... Co-authored-by: konsti <konstin@mailbox.org>	2025-10-07 23:17:42 +00:00
chance	111ed6fc94	Update uv pip compile args in layout.md (#16155) ... <!-- 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 Corrects example command for generating pylock.toml from requirements.in ## Test Plan Local preview	2025-10-07 12:32:02 -05:00
Zanie Blue	252f887338	Bump version to 0.8.24 (#16146)	2025-10-07 03:03:01 +00:00
Zanie Blue	00d3aa3780	Bump version to 0.8.23 (#16119)	2025-10-04 12:46:01 -05:00
konsti	1bdb096599	Document transparent x86_64 emulation on aarch64 (#16041)	2025-10-02 18:31:33 +02:00
Zanie Blue	ade2bdbd2a	Bump version to 0.8.22 (#16005)	2025-09-23 14:43:48 -05:00
Charlie Marsh	f64da27450	Bump version to v0.8.21 (#16001)	2025-09-23 13:55:19 +00:00
Zanie Blue	3e6fd0b775	Bump version to 0.8.20 (#15998)	2025-09-22 22:34:27 +00:00
Zanie Blue	9cabf63cd0	Add package level conflicts to the conflicting dependencies docs (#15963)	2025-09-22 09:07:07 -05: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
Zanie Blue	1d7d7fdf00	Document pyodide support (#15962)	2025-09-20 13:11:44 -05:00
Zanie Blue	fc7c2f8b50	Bump version to 0.8.19 (#15953)	2025-09-19 14:34:41 -05:00
Zanie Blue	c4c47814a8	Bump version to 0.8.18 (#15920)	2025-09-17 16:13:41 -05:00
konsti	5633d3abe4	Document cache-keys for native build backends (#15811) ... Update note for https://github.com/astral-sh/uv/pull/15705#issuecomment-3285240646 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-14 14:20:17 +00:00
Aria Desires	8917b00fd9	add docs for dependency group requires-python (#14282) ... I specifically show more details than necessary in the example to make it more clear that this is *NOT* the normal dependency-groups table. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-12 13:15:27 +00:00
Zanie Blue	7789f5b217	Bump version to 0.8.17 (#15776)	2025-09-10 14:59:48 -05:00
Charlie Marsh	2de677b0d3	Bump version to v0.8.16 (#15761) ... Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-09-09 21:41:56 -04:00
Charlie Marsh	70cb0df7c2	Bump version to v0.8.15 (#15648)	2025-09-03 02:10:58 +00: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	4d79fd2c04	Add documentation on the uv credential store and CLI (#15597)	2025-09-02 13:16:52 -05:00
Zanie Blue	cc4be0f2ba	Add the native keyring to the documentation (#15596)	2025-09-02 13:16:52 -05:00
Anthony Wu	5f0ec6805a	Fix simple typo for python that ends in -m (#15624) ... ## Summary Fix simple doc typo `s/pythom/python` ## Test Plan Doc string update, proposing accept as-is.	2025-09-01 21:43:48 -04:00
Zanie Blue	af856fb883	Bump version to 0.8.14 (#15576)	2025-08-28 21:25:02 +00:00
Zanie Blue	bf189c5414	Split the "Authentication" page into sections (#15575) ... In preparation for more content for #15570	2025-08-28 15:45:31 -05:00
Zanie Blue	960714d4d6	Tweak some documentation headings (#15556) ... Just some nits I want to make incremental progress on	2025-08-27 18:16:52 +00:00
konsti	db4dfb4cf9	Add logging to the uv build backend (#15533) ... Add support for `RUST_LOG` to the uv build backend. While we were previously using logging statements in the uv build backend, they could only be shown when when using the direct build fast path through uv, as there was no tracing subscriber to write log messages out. This means no debug logging when using the build backend through pip, `python -m build`, an incompatible version of uv, or any other build frontend; No option to figure why includes and excludes behave the way they do. This PR closes this gap by adding a tracing subscriber. The only option to enable it is `RUST_LOG`, as we don't have a CLI. The formatting style is the same as for uv, and color is also support in the same way, albeit only through anstream's support for TTYs and environment variables. We recommend only `RUST_LOG=uv=debug` and `RUST_LOG=uv=verbose` in the docs, but this can be used to debug into crates such as `glob`, too. <img width="1008" height="325" alt="image" src="https://github.com/user-attachments/assets/d33df219-750b-46a2-b3b4-8895aa137ab9" /> **Before** ``` $ pip wheel . -v [...] Looking in links: /home/konsti/projects/uv/target/wheels/ Processing /home/konsti/projects/uv/scripts/packages/built-by-uv Running command pip subprocess to install build dependencies Looking in links: /home/konsti/projects/uv/target/wheels/ Processing /home/konsti/projects/uv/target/wheels/uv_build-0.8.13-py3-none-manylinux_2_39_x86_64.whl Installing collected packages: uv_build Successfully installed uv_build-0.8.13 Installing build dependencies ... done Running command Getting requirements to build wheel Getting requirements to build wheel ... done Running command Preparing metadata (pyproject.toml) Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: built-by-uv Running command Building wheel for built-by-uv (pyproject.toml) Error: Unsupported glob expression in: `tool.uv.build-backend.*-exclude` Caused by: Invalid character `!` at position 10 in glob: `**/build-*!$§%!½¼²¼³¬!§%$§%.h`. hint: Characters can be escaped with a backslash error: subprocess-exited-with-error × Building wheel for built-by-uv (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. full command: /usr/bin/python3 /usr/lib/python3/dist-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_wheel /tmp/tmpow1illc9 cwd: /home/konsti/projects/uv/scripts/packages/built-by-uv Building wheel for built-by-uv (pyproject.toml) ... error ERROR: Failed building wheel for built-by-uv Failed to build built-by-uv ERROR: Failed to build one or more wheels ``` **After** ``` $ RUST_LOG=uv=debug pip wheel . -v [...] Looking in links: /home/konsti/projects/uv/target/wheels/ Processing /home/konsti/projects/uv/scripts/packages/built-by-uv Running command pip subprocess to install build dependencies Looking in links: /home/konsti/projects/uv/target/wheels/ Processing /home/konsti/projects/uv/target/wheels/uv_build-0.8.13-py3-none-manylinux_2_39_x86_64.whl Installing collected packages: uv_build Successfully installed uv_build-0.8.13 Installing build dependencies ... done Running command Getting requirements to build wheel Getting requirements to build wheel ... done Running command Preparing metadata (pyproject.toml) DEBUG Writing metadata files to /tmp/pip-modern-metadata-l_kh78cj DEBUG Found PEP 639 license declarations, using METADATA 2.4 DEBUG License files match: `LICENSE-APACHE` DEBUG License files match: `LICENSE-MIT` DEBUG License files match: `third-party-licenses/PEP-401.txt` Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: built-by-uv Running command Building wheel for built-by-uv (pyproject.toml) DEBUG Checking metadata directory /tmp/pip-modern-metadata-l_kh78cj/built_by_uv-0.1.0.dist-info DEBUG Found PEP 639 license declarations, using METADATA 2.4 DEBUG License files match: `LICENSE-APACHE` DEBUG License files match: `LICENSE-MIT` DEBUG License files match: `third-party-licenses/PEP-401.txt` DEBUG Writing wheel at /tmp/pip-wheel-bu6to9i7/built_by_uv-0.1.0-py3-none-any.whl DEBUG Wheel excludes: ["__pycache__", "*.pyc", "*.pyo", "build-*!$§%!½¼²¼³¬!§%$§%.h", "/src/built_by_uv/not-packaged.txt"] Error: Unsupported glob expression in: `tool.uv.build-backend.*-exclude` Caused by: Invalid character `!` at position 10 in glob: `**/build-*!$§%!½¼²¼³¬!§%$§%.h`. hint: Characters can be escaped with a backslash error: subprocess-exited-with-error × Building wheel for built-by-uv (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. full command: /usr/bin/python3 /usr/lib/python3/dist-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_wheel /tmp/tmpjrxou13a cwd: /home/konsti/projects/uv/scripts/packages/built-by-uv Building wheel for built-by-uv (pyproject.toml) ... error ERROR: Failed building wheel for built-by-uv Failed to build built-by-uv ERROR: Failed to build one or more wheels ``` (There is no color in the above uv log statements, as pip doesn't register as a TTY) Fixes #12723	2025-08-27 09:14:00 +02:00
Giuseppe Di Giorno	f1647838ae	Move Resolver to new Internals section in the Reference (#15465) ... ## Summary Move the Resolver reference into a new Internals section in the reference. Add the new nav item, fix internal linking to the new path, fix server side redirect to the new path for external traffic via redirect_maps, fix non existent anchor in "docs/concepts/projects/dependencies.md" Closes #15412	2025-08-22 19:26:16 -05:00
Zanie Blue	ede75fe628	Bump version to 0.8.13 (#15423)	2025-08-21 13:52:39 -05: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
Zsolt Dollenstein	5271ce5e24	Fix typo in extra-build-dependencies docs (#15390) ... ## Summary Smol but important typo.	2025-08-20 12:39:59 +01:00
Zanie Blue	f784c334cf	Bump version to 0.8.12 (#15364)	2025-08-18 22:14:51 +00:00
Charlie Marsh	fa3c20a177	Document improvements to build-isolation setups (#15326) ... ## Summary There's a lot here (maybe it should go somewhere else?), but this is a complex topic and I wanted to include a lot of copy-pasteable examples for common cases. Closes https://github.com/astral-sh/uv/issues/10694. Closes https://github.com/astral-sh/uv/issues/13959. Closes https://github.com/astral-sh/uv/issues/15248. Closes https://github.com/astral-sh/uv/issues/15316.	2025-08-18 16:15:35 -05:00
Zanie Blue	f892276ac8	Bump version to 0.8.11 (#15287)	2025-08-14 14:21:10 -05:00
Zanie Blue	7e817bafde	Bump version to 0.8.10 (#15257)	2025-08-13 20:06:08 +00:00
Zanie Blue	68c0bf8a2c	Bump version to 0.8.9 (#15229)	2025-08-11 21:07:59 -05:00
Zanie Blue	9a54754b0a	Bump version to 0.8.8 (#15184)	2025-08-08 19:03:07 -05:00
Zanie Blue	8a22572338	Bump version to 0.8.7 (#15173)	2025-08-08 14:42:23 -05:00