4903 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Charlie Marsh	b98bdc818f	Add support for pip list --outdated (#8872) ... ## Summary Closes https://github.com/astral-sh/uv/issues/2150.	2024-11-07 02:32:30 +00:00
Charlie Marsh	273f453e75	Use no reporter by default in cache clean (#8868)	2024-11-06 17:07:10 +00:00
Jo	738f4245a5	Add docs/configuration/environment.md to code change list (#8859) ... See #8858, the `cargo dev generate-all` step should not be skipped.	2024-11-06 11:44:42 -05:00
Jo	dcd24b7c42	Add progress bar for uv cache clean (#8857) ... ## Summary Closes #8786	2024-11-06 11:43:43 -05:00
Charlie Marsh	987d778631	Respect dynamic version updates in uv lock (#8867) ... ## Summary Closes https://github.com/astral-sh/uv/issues/8866.	2024-11-06 11:40:23 -05:00
Jo	814b4d159c	Add MSRV build to CI (#8855) ... ## Summary Closes #8451	2024-11-06 11:22:13 -05:00
Jo	9f81db7d1d	Use cache in windows clippy job (#8852) ... Place the `Swatinem/rust-cache@v2` step after `setup-dev-drive.ps1` to ensure the correct directories are cached.	2024-11-05 23:05:34 -06:00
Zanie Blue	129c6f61d4	Revert "Using --build-backend in uv init implies --package (#8837)" (#8850) ... This reverts commit 515993c743 from https://github.com/astral-sh/uv/pull/8837 as it was already implemented differently in https://github.com/astral-sh/uv/pull/8593 and I missed it	2024-11-06 01:36:11 +00:00
Udi Oron	8963de26a7	docs: fix uv python install docs to use an exisigin pypy version (#8845) ... The current docs call to install pypy@3.12 that does not exist yet. Change it to install pypy@3.10	2024-11-05 16:13:58 -06:00
Charlie Marsh	26e3511ebd	Respect fork markers in --resolution-mode=lowest-direct (#8839) ... ## Summary Previously, given: ```toml dependencies = [ "pycountry >= 22.1.10", "setuptools >= 50.0.0; python_version>='3.12'" ] ``` We'd solve for the lowest version of setuptools (with _no_ lower-bound constraint) in the `python_version < '3.12'` complement. Closes https://github.com/astral-sh/uv/issues/8819.	2024-11-05 21:09:38 +00:00
Charlie Marsh	d238642d76	Allow semicolons directly after direct URLs (#8836) ... ## Summary Like pip, we now allow the semicolon to directly proceed the URL (but require that it's either preceded or followed by a space): ``` # OK ./test.whl; sys_platform == 'darwin' # OK ./test.whl ;sys_platform == 'darwin' # Error ./test.whl;sys_platform == 'darwin' ``` Closes https://github.com/astral-sh/uv/issues/8831.	2024-11-05 16:07:07 -05:00
Zanie Blue	515993c743	Using --build-backend in uv init implies --package (#8837)	2024-11-05 14:15:55 -06:00
Charlie Marsh	eeb8736448	Show dedicated error for trailing ; on URL and path requirements (#8835) ... ## Summary I think we lost this error in a prior refactor. I've added an end-to-end test too.	2024-11-05 13:29:36 -05:00
Andrew Gallant	fae03a7287	uv-pep440: DRY up VersionSmall implementation (#8834) ... This PR simplifies the VersionSmall implementation a bit by utilizing more constants. That is, if the bit-level format changes, *most* of those changes should be implementable by just changing the constants. Previously, you would need to audit and tweak the code as well. (The exception here is `push_release`. If the release segment bit format is changed, then that function will need to be tweaked. I didn't think it was worth over-complicating things to make its implementation more general.)	2024-11-05 13:26:19 -05:00
Charlie Marsh	23ea5df76a	Warn on failure to query system configuration file (#8829) ... ## Summary See: #8828.	2024-11-05 16:11:38 +00:00
Robert Deaton	177fafceb4	Enable support for arbitrary git transports (#8769)	2024-11-05 08:55:15 +01:00
Charlie Marsh	23afc608b8	Update pip-and-uv strictness example (#8822) ... ## Summary pip now enforces this too! Let's use a different example. Closes https://github.com/astral-sh/uv/issues/8412.	2024-11-04 21:32:45 -05:00
Zanie Blue	61ed2a236a	Bump version to 0.4.30 (#8820)	2024-11-04 18:52:57 -06:00
konsti	c39936e9c8	Publish: Hint at --skip-existing -> --check-url transition (#8803) ... See https://github.com/astral-sh/uv/pull/8531#issuecomment-2442698889, we hint users coming from twine to use `--check-url` instead. > `uv publish` does not support `--skip-existing`, use `--check-url` with the simple index URL instead. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2024-11-04 23:21:01 +00:00
Charlie Marsh	f8ec7975c8	Update Packse snapshots (#8795) ... ## Summary The diff here is challenging because it looks like some tests got reordered.	2024-11-04 16:17:43 -05:00
Zanie Blue	fb1d679f69	Improve interactions with existing Python executables during install (#8733) ... Previously, we'd use the `--reinstall` flag to determine if we should replace existing Python executables in the bin directory during an install. There are a few problems with this: - We replace executables we don't manage - We can replace executables from other uv Python installations during reinstall (surprising) - We don't do the "right" thing when installing patch versions e.g. installing `3.12.4` then `3.12.6` would fail without the reinstall flag In `uv tool`, we have separate `--force` and `--reinstall` concepts. Here we separate the flags (`--force` was previously just a `--reinstall` alias) and add inspection of the existing executables to inform a decision on replacement. In brief, we will: - Replace any executables with `--force` - Replace executables for the same installation with `--reinstall` - Replace executables for an older patch version by default	2024-11-04 20:22:44 +00:00
Zanie Blue	6a6b9af466	Fix test case on main (#8816)	2024-11-04 19:50:59 +00:00
Charlie Marsh	a42c09fdfb	Add support for .env and custom env files in uv run (#8811) ... ## Summary This PR pulls in https://github.com/astral-sh/uv/pull/8263 and https://github.com/astral-sh/uv/pull/8463, which were originally merged into the v0.5 tracking branch but can now be committed separately, as we've made `.env` loading opt-in. In summary: - `.env` loading is now opt-in (`--env-file .env`). - `.env` remains supported on `uv run`, so it's meant for providing environment variables to the run command, rather than to uv itself. --------- Co-authored-by: Eduardo González Vaquero <47718648+edugzlez@users.noreply.github.com>	2024-11-04 14:26:05 -05:00
Andrew Gallant	224622b089	uv/tests: make python_version < '0' regression test smaller (#8809) ... Running this test manually on the latest release shows that it still emits a `python_version < '0'` marker: $ uv-0.4.29 pip compile requirements.in -c constraints.txt --annotation-style line --python 3.10 --universal | rg "< '0'" Resolved 151 packages in 97ms apache-airflow-providers-common-sql==1.19.0 ; python_version < '0' # via apache-airflow-providers-sqlite That is, even though this is a smaller test, it's still testing the same bug. This is about twice as fast on my machine. It's probably still worth moving to a packse test, but this was quick to do.	2024-11-04 11:10:17 -05:00
Andrew Gallant	acaed763b7	uv: use ResolverEnvironment instead of ResolverMarkers ... This updates the surrounding code to use the new ResolverEnvironment type. In some cases, this simplifies caller code by removing case analysis. There *shouldn't* be any behavior changes here. Some test snapshots were updated to account for some minor tweaks to error messages. I didn't split this up into separate commits because it would have been too difficult/costly.	2024-11-04 11:09:06 -05:00
Andrew Gallant	44c9ef6aea	uv-resolver: add new ResolverEnvironment type ... This type is intended to replace `ResolverMarkers`. The main difference between them is that this type encapsulates more decision making by un-exporting the different cases. So instead of callers needing to do explicit case analysis depending on the type of resolver environment, callers instead use methods that know how to do the right thing. In the next commit, there are at least a few cases where this greatly simplifies case analysis on the caller side. The motivation for this type is to centralize decision making about forking. In particular, we want to expand forking to include conflicting groups instead of just `MarkerTree`. So to a certain extent, the refactor here is about removing bare use of `MarkerTree` in favor of a more purpose built type that encapsulates the forking logic. The encapsulation is not quite perfect here. I expect to improve on it a bit once we add support for conflicting groups. This is split off from the subsequent commit (that makes use of `ResolverEnvironment`) so that it's a bit easier to review the addition in isolation.	2024-11-04 11:09:06 -05:00
Andrew Gallant	fccd48ce61	uv-normalize: add as_str method ... `ExtraName` did implement `AsRef<str>`, but that should generally only be used in a context with an `AsRef<str>` generic bound. If you just want a `&str` from a concrete `ExtraName`, then a specific method for that purpose should be used.	2024-11-04 11:09:06 -05:00
Zanie Blue	6250b900b7	Allow managed downloads with --python-preference system (#8808) ... Closes https://github.com/astral-sh/uv/issues/8804	2024-11-04 07:45:24 -06:00
Tim de Jager	d82607d038	Extend BaseClient to accept extra middleware (#8807) ... This PR is a revival of #3502, albeit in a much simpler form. This would allow for different middlewares like authentication and such, useful for if you want to deviate from the keychain authentication methods when using uv as a library. @zanieb I hope I made the changes as you noted you wanted to see them :) Happy to add/change anything you need.	2024-11-04 07:04:26 -06:00
Tim de Jager	ef8724c979	Add From for FlatDistributions struct (#8800) ... Co-authored-by: konsti <konstin@mailbox.org>	2024-11-04 08:41:39 +00:00
renovate[bot]	a052418dcd	Update Rust crate which to v7 (#8794)	2024-11-03 21:15:17 -05:00
renovate[bot]	e77ecfd2bd	Update Rust crate procfs to 0.17.0 (#8793)	2024-11-03 21:15:10 -05:00
renovate[bot]	f234ec37d5	Update Rust crate axoupdater to 0.8.0 (#8792)	2024-11-03 21:15:04 -05:00
renovate[bot]	97763d2ade	Update pre-commit dependencies (#8791)	2024-11-03 21:14:58 -05:00
renovate[bot]	15d003a65f	Update Rust crate thiserror to v1.0.67 (#8790)	2024-11-03 21:14:54 -05:00
renovate[bot]	aa96307273	Update Rust crate syn to v2.0.87 (#8789)	2024-11-03 21:14:51 -05:00
renovate[bot]	a0cbf5d32b	Update Rust crate anyhow to v1.0.92 (#8787)	2024-11-03 21:14:31 -05:00
konsti	fd6b6aca0f	Fix indentation level in test publish script (#8785)	2024-11-03 22:42:00 +01:00
konsti	b2afcf2f2c	Retrying parsing in test_publish.py (#8784)	2024-11-03 20:56:19 +00:00
Charlie Marsh	bf79d985ee	Allow incompatible requires-python for source distributions with static metadata (#8768) ... ## Summary At present, when we have a Python requirement and we see a wheel, we verify that the Python requirement is compatible with the wheel. For source distributions, though, we verify that both the Python requirement _and_ the currently-installed version are compatible, because we assume that we'll need to build the source distribution in order to get metadata. However, we can often extract source distribution metadata _without_ building (e.g., if there's a `pyproject.toml` with no dynamic keys). This PR thus modifies the source distribution handling to defer that incompatibility ("We couldn't get metadata for this project, because it has no static metadata and requires a higher Python version to run / build") until we actually try to build the package. As a result, you can now resolve source distribution-only packages using Python versions below their `requires-python`, as long as they include static metadata. Closes https://github.com/astral-sh/uv/issues/8767.	2024-11-03 19:03:55 +00:00
samypr100	647494b998	docs: env var doc improvements (#8777) ... ## Summary * Env docs now support anchors, which allows sending a link to someone with a direct reference to an env var or cross-reference them in the docs. * Marked additional env vars as hidden from the docs due to their internal use * Updates some tests still using literals to use the static env vars ## Test Plan <img width="1370" alt="env_var_anchors" src="https://github.com/user-attachments/assets/52ae1caa-5199-4798-9eb5-81b8f5b57c24">	2024-11-03 13:56:17 -05:00
konsti	f52814e729	Fix no_binary_only_binary test (#8776)	2024-11-03 15:52:14 +00:00
Jo	3dfedf1fef	Generate environment variables doc from code (#8493) ... ## Summary Resolves #8417 I've just begun learning procedural macros, so this PR is more of a proof of concept. It's still a work in progress, and I welcome any assistance or feedback.	2024-11-03 08:31:38 -06:00
k_fukuchi	545a55f58f	Fix indentation in projects.md (#8772) ... ## Summary Fix indentation in `projects.md`	2024-11-03 08:28:08 -06:00
Zanie Blue	2ed94745a2	Show full error chain on tool upgrade failures (#8753) ... As reported in https://github.com/astral-sh/uv/issues/8555	2024-11-02 11:55:41 -05:00
Charlie Marsh	d3e50a2376	Enable --all-packages --frozen in uv sync and uv export (#8760) ... ## Summary This PR improves the interaction of `--frozen` such that we reduce the dependency on the `pyproject.toml` and increase the dependency on the `uv.lock`. Specifically, we now read the list of workspace members from the `uv.lock` rather than the `pyproject.toml`, which means we don't need to discover the member `pyproject.toml` files in order to perform a `uv sync --frozen --all-packages`.	2024-11-02 02:48:55 +00:00
Charlie Marsh	b36ae6d5ae	Add support for uv export --all-packages (#8742) ... ## Summary Same as the other PRs, but for `uv export`.	2024-11-02 02:25:29 +00:00
Charlie Marsh	3808b61fc1	Add support for uv run --all-packages (#8741) ... ## Summary Closes https://github.com/astral-sh/uv/issues/8724.	2024-11-02 02:16:06 +00:00
Charlie Marsh	3c9dd97fe9	Add support for uv sync --all-packages (#8739) ... ## Summary This PR enables `uv sync --all-packages` to sync all packages in a workspace. It removes a common use-case for the legacy non-`[project]` packages that we're trying to move away from. Closes https://github.com/astral-sh/uv/issues/8724.	2024-11-02 01:55:08 +00:00
Andrew Gallant	58a9811881	fix bug where python_version < '0' could appear in a final resolution (#8759) ... This PR fixes a bug where it was possible for dependencies to be included in a final resolution with markers that always evaluate to false. Specifically, `python_version < '0'`. While we do filter based on Python markers during forking, it turns out that the markers for each fork are "combined" *after* this filtering step. But the process of combination can result in a more specific marker that is always false for the configured Python requirement. This could result in dependencies with markers that are always false (like `python_version < '0'`) appearing in the resolution. The first commit in this PR adds a regression test (with an undesirable result), and the second commit fixes the regression and updates the test. Fixes #8676	2024-11-01 20:11:40 +00:00