271 commits

Author	SHA1	Message	Date
Zanie Blue	f0ec9fd44a	Bump version to 0.6.4 (#11934)	2025-03-03 16:04:11 -06:00
Charlie Marsh	a1690203cf	Avoid fallback to PyPI in mixed CPU/CUDA example (#11115) ... ## Summary This is roughly equivalent, but gets the non-`+cpu` macOS build from the PyTorch index rather than PyPI. It seems a bit simpler? Though up for debate.	2025-03-02 22:35:32 -05:00
Mathieu Kniewallner	368f9a82d9	docs: rework alternative indexes documentation (#10826) ... ## Summary Closes #9867. Update alternative indexes documentation to use `[[tool.uv.index]]` and the associated environment variables instead of `UV_INDEX`. This also globally reworks the documentation by: - adding AWS CodeArtifact keyring example - adding packages publishing examples for all providers - making it more consistent for all providers It might be best to show how to publish packages only once for all providers, but the publish URL usually being different than the URL used to retrieve packages, even if this duplicates things, it might still be more straightforward for users to see exactly what is needed for each provider. ## Test Plan Manually tested retrieving packages from AWS CodeArtifact and GCP Artifact Registry using both token and keyring. Could not test: - Publishing packages - Azure Artifacts (not using it at all) --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-02-26 09:52:44 -06:00
Aria Desires	a0b9f22a21	Bump version to 0.6.3 (#11759)	2025-02-24 17:25:01 -05:00
Zanie Blue	6d3614eece	Bump version to 0.6.2 (#11630)	2025-02-19 13:11:11 -06:00
FishAlchemist	555bf89b38	Add document for specifying Python interpreter in tool installation and upgrade commands. (#11598) ... <!-- 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 Just to add the section for installing and upgrading uv tool, specifying the Python version, in the document. Originally, it was planned to add a markdown block (header) for representation, but it was felt to be a bit redundant, so it ended up being like this. close https://github.com/astral-sh/uv/issues/11536 ## Test Plan Run doc server with strict mode in local. (``mkdocs serve -f mkdocs.public.yml --strict``)  <!-- How was it tested? --> --------- Signed-off-by: FishAlchemist <48265002+FishAlchemist@users.noreply.github.com> Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-02-18 11:45:58 -06:00
Zanie Blue	c91ee82a82	Bump version to 0.6.1 (#11580)	2025-02-17 11:57:47 -06:00
Zanie Blue	591f38c25e	Bump version to v0.6.0 (#11496) ... Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2025-02-14 11:55:54 -06:00
Aria Desires	9138b35c66	Create main.py instead of hello.py in uv init (#10369) ... Initially it seemed like `app.py` might be slightly more desirable but people seem to overwhelmingly favour `main.py` as a good "generic" name. Fixes #7782	2025-02-13 16:17:49 -06:00
Zanie Blue	e38ac4900d	Bump version to 0.5.31 (#11459)	2025-02-12 14:45:22 -06:00
Lewis	0b4a349173	Update scripts docs with package indexes (#11443) ... ## Summary The [current scripts docs page](https://docs.astral.sh/uv/guides/scripts/) doesn't include detail on how to use a custom package index when setting up a script. I believe this might be because it didn't use to work (see #6688 ) but it now does (thanks for that, by the way! 😄) Given it's a useful feature, I suggest adding a quick example to the scripts page, with the details of authentication, etc. left to the main `indexes.md` doc. I'd also suggests that this closes #6688, though it doesn't actually add that feature - that appears to have already been done :) ## Test Plan No testing is needed, I think! --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-02-12 07:52:22 -06:00
Valentin Oliver Loftsson	5e15881dcc	Update alternative-indexes.md to use UV_INDEX instead of UV_EXTRA_INDEX_URL (#11381) ... <!-- 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 Use `UV_INDEX` instead of the deprecated `UV_EXTRA_INDEX_URL`. <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan It is a minor documentation change. <!-- How was it tested? -->	2025-02-11 09:19:20 -05:00
Charlie Marsh	ca49495e4b	Bump version to v0.5.30 (#11405)	2025-02-10 21:42:31 +00:00
Zanie Blue	ca73c47543	Bump version to 0.5.29 (#11267)	2025-02-05 19:59:29 -05:00
Zanie Blue	c64965273f	Misc. improvements to the documentation (#11255)	2025-02-05 17:22:09 -06:00
Zanie Blue	2105b8a89d	Minor touchups to the Docker provenance docs (#11252)	2025-02-05 17:09:15 +00:00
Charlie Marsh	fea00dcdd5	Bump version to v0.5.28 (#11228)	2025-02-04 20:28:43 -05:00
Martijn Pieters	04374b03cc	Docs on how to verify uv docker image attestations (#11140) ... As [requested by @zanieb](https://github.com/astral-sh/uv/pull/8685#issuecomment-2627556992).	2025-02-04 15:38:19 -06:00
Zanie Blue	73e9928d40	Bump version to 0.5.27 (#11201)	2025-02-03 16:55:36 -06:00
Charlie Marsh	2dfeafbaa4	Set UV_PYTHON in Jupyter kernels (#11155) ... ## Summary It turns out activating the kernel does not change `VIRTUAL_ENV`, so we still install into the environment the Jupyter environment, rather than the project environment. Unfortunately, after this change, we do still show a warning on `uv add`: ``` warning: `VIRTUAL_ENV=/Users/crmarsh/.cache/uv/archive-v0/3bddKDdYXuX2w57Fu6itL` does not match the project environment path `.venv` and will be ignored ``` `uv pip install` works without warning. Closes #11154.	2025-02-01 16:54:34 -05:00
Zanie Blue	5ef3d51390	Bump version to 0.5.26 (#11119)	2025-01-30 15:37:00 -06:00
Zanie Blue	e0a19be825	Touch-ups to the Python install guide (#11116)	2025-01-30 13:56:53 -06:00
Charlie Marsh	7531bb8669	Upgrade PyTorch version in documentation (#11114) ... ## Summary PyTorch 2.6.0 is now GA!	2025-01-30 14:05:13 -05:00
Charlie Marsh	658ca89fb1	Use sys_platform in lieu of platform_system in PyTorch docs (#11113) ... ## Summary This is what we use in the lockfile. I believe it's preferable, and it's also more concise.	2025-01-30 19:01:52 +00:00
Charlie Marsh	9f8cd92bd3	Use positive (rather than negative) markers in PyTorch examples (#11112) ... ## Summary Maybe slightly controversial because it's more verbose, but we really want to limit these indexes to Linux and Windows, rather than ignoring them on Darwin. E.g., we'd also want to ignore them on other platforms. Further down, I use markers that look like this in the more complete examples, so this feels more consistent.	2025-01-30 14:00:35 -05:00
Charlie Marsh	70507b7898	Add PyTorch XPU instructions to the PyTorch guide (#11109) ... ## Summary Closes https://github.com/astral-sh/uv/issues/11079.	2025-01-30 13:48:52 -05:00
Danilo Rezende	eb8ffa4981	Update documentation for running in a container (#11052) ... This PR rewords the instructions for using uv in a container. I'm a new user and was somewhat confused by it, so I've rewritten it as I'd have liked to have read it. It makes it more clear what distroless means, to avoid confusion with other projects that ship OS files with an image with its tag name clear of qualifiers(`astral-sh/uv`, in this case). An example of that is caddy, which ships with alpine. This also modifies the original example to use a distroful image instead of distroless one while #8635 doesn't get resolved. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-01-30 00:17:58 +00:00
Zanie Blue	a3049ecf69	Fix broken link (#11081)	2025-01-29 19:41:18 +00:00
Zanie Blue	2ca51501ed	Shorten "Using existing Python versions" nav item so it fits on one line (#11077)	2025-01-29 19:04:11 +00:00
Florian Greinacher	9fc24b2ac5	docs: suggest copy linking for GitLab integration guide (#11067) ... ## Summary Hardlinking does not work in that context and raises a warning. Setting the link mode to copy makes the warning go away. ## Test Plan Tested on gitlab.com and our self-hosted GitLab instance. Before changing the link mode: 8986967570 After changing the link mode: 8987026307. ⚒️ with ❤️ by [Siemens](https://opensource.siemens.com/) --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-01-29 17:58:14 +00:00
Bob Whitelock	baec42c494	Update Dependabot links (#11054) ... ## Summary The latter issue has been closed in favour of the former, so just link the one issue Dependabot is using to track this. ## Test Plan N/A --- Thanks!	2025-01-29 08:06:08 -06:00
Zanie Blue	9c07c3fc5b	Bump version to 0.5.25 (#11042)	2025-01-28 15:40:43 -06:00
Ryan	90a4178c7a	[docs/integration/docker] add sha pinning tip (#10955) ... <!-- 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? --> As requested in https://github.com/astral-sh/uv/issues/6565, this adds a tip discussing the ability to pin the image to a specific SHA digest and why it may be useful. ## Test Plan <!-- How was it tested? --> Start serving the documentation locally ```shell uvx --with-requirements docs/requirements.txt -- mkdocs serve -f mkdocs.public.yml ``` Then navigate to http://127.0.0.1:8000/uv/guides/integration/docker/ to see the tool tip being rendered properly --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-01-27 18:29:23 +00:00
Paul	e8d6b330a3	tiny typo (duplicate word) (#10959) ... Fix an apparent typo	2025-01-25 10:30:10 -06:00
Zanie Blue	42fae925c4	Bump version to 0.5.24 (#10922)	2025-01-23 17:26:59 -06:00
Charlie Marsh	ba42467f1b	Bump version to v0.5.23 (#10879)	2025-01-23 00:26:10 +00:00
3sh V	cee8770cb0	Update pre-commit documentation (#10756) ... ## Summary Added missing `repos:` line to make the example config complete --------- Co-authored-by: Rajesh Veeranki <rveeranki@d4q74qfn2y.agoda.local> Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-01-21 22:46:18 +00:00
Charlie Marsh	4574ced370	Bump version to v0.5.22 (#10829)	2025-01-21 17:03:55 -05:00
Mathieu Kniewallner	7a14ea639e	docs: manually bump pre-commit refs (#10814) ... ## Summary rooster should pick those up, but those 2 references were added to 0.5.8 while a 0.5.9 was already released (f5add0ca5e), so they never got bumped automatically. I've searched for other cases like this in the documentation on other versions, just in case, and it seems that this is the only case.	2025-01-21 09:28:28 -05:00
Charlie Marsh	54bb5a38a4	Add invoke instructions to the AWS Lambda guide (#10805) ... ## Summary Closes https://github.com/astral-sh/uv/issues/10804.	2025-01-21 03:40:42 +00:00
Charlie Marsh	3478c068bb	Bump version to v0.5.21 (#10723)	2025-01-17 20:53:36 +00:00
Charlie Marsh	1c17662b37	Bump version to v0.5.20 (#10659)	2025-01-15 23:18:06 +00:00
Zanie Blue	a7f13e0e0b	Bump version to 0.5.19 (#10643)	2025-01-15 20:56:43 +00:00
FishAlchemist	9736868908	Add meta titles to documents in guides, excluding integration documents. (#10539) ... ## Summary Add meta titles to documents in guides, excluding integration documents. <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan ``uvx --with-requirements docs/requirements.txt -- mkdocs build --strict -f mkdocs.public.yml`` <details> <summary>Build Result</summary> * ``guides/install-python`` ```html ... <meta name="description" content="Guide to install specific Python versions, manage existing installations, and automate downloads with uv."> ... <title>Install and Manage Python | uv</title> ... ``` * ``guides/projects`` ```html ... <meta name="description" content="Guide to create, manage, and build Python projects with uv, including dependencies and distributions."> ... <title>Working on projects | uv</title> ... ``` * ``guides/publish`` ```html ... <meta name="description" content="Guide to build and publish Python packages using uv"> ... <title>Publishing a package | uv</title> ... ``` * ``guides/scripts`` ```html ... <meta name="description" content="Run Python scripts quickly and manage dependencies efficiently using uv. Learn about inline metadata and more."> ... <title>Run Scripts | uv</title> ... ``` * ``guides/tools`` ```html ... <meta name="description" content="Guide to run, install, and upgrade Python tools using uv."> ... <title>Using tools | uv</title> ... ``` </details> --------- Co-authored-by: Charles Tapley Hoyt <cthoyt@gmail.com> Co-authored-by: Zanie Blue <contact@zanie.dev>	2025-01-15 14:12:55 -06:00
sergue1	15e20501d1	typo (#10538) ... fix typo in docs	2025-01-12 09:07:04 -06:00
Charlie Marsh	27d1bad550	Bump version to v0.5.18 (#10499)	2025-01-11 14:38:26 +00:00
Charlie Marsh	c198e2233e	Bump version to v0.5.17 (#10480)	2025-01-10 15:52:56 -05:00
Charlie Marsh	129a75e2d0	Add meta descriptions for remaining guides (#10450) ... ## Summary Closes https://github.com/astral-sh/uv/issues/10418.	2025-01-09 17:39:00 -05:00
Charlie Marsh	d77598a08c	Use Windows-specific instructions in Jupyter guide (#10446) ... ## Summary Closes https://github.com/astral-sh/uv/issues/10407.	2025-01-09 16:43:09 -05:00
Charlie Marsh	19589e0614	Add meta descriptions for some guides (#10421) ... ## Summary Part of: https://github.com/astral-sh/uv/issues/10418.	2025-01-09 15:50:16 +00:00