4972 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
konsti	bb70382dac	Build backend: Default excludes (#9552) ... When adding excludes, we usually don't want to include python cache files. On the contrary, I haven't seen any project in my ecosystem research that would want any of `__pycache__`, `*.pyc`, `*.pyo` to be included. By moving them behind a `default-excludes` toggle, they are always active even when defining custom excludes, but can be deactivated if the user so chooses. With includes and excludes being this small again, we can roll back the include-exclude anchored difference to always using anchored globs (i.e. you would need to use `**/build-*.h` below). A pyproject.toml with custom settings with the change applied: ```toml [project] name = "foo" version = "0.1.0" readme = "README.md" license-files = ["LICENSE*", "third-party-licenses/*"] [tool.uv.build-backend] # A file we need for the source dist -> wheel step, but not in the wheel itself (currently unused) source-include = ["data/build-script.py"] # A temporary or generated file we want to ignore source-exclude = ["/src/foo/not-packaged.txt"] # Headers are build-only wheel-exclude = ["build-*.h"] [tool.uv.build-backend.data] scripts = "scripts" data = "assets" headers = "header" [build-system] requires = ["uv>=0.5.5,<0.6"] build-backend = "uv" ```	2024-12-01 14:09:55 +01:00
konsti	dfcceb6a1d	Build backend: Revamp include/exclude (#9525) ... When building the source distribution, we always need to include `pyproject.toml` and the module, when building the wheel, we always include the module but nothing else at top level. Since we only allow a single module per wheel, that means that there are no specific wheel includes. This means we have source includes, source excludes, wheel excludes, but no wheel includes: This is defined by the module root, plus the metadata files and data directories separately. Extra source dist includes are currently unused (they can't end up in the wheel currently), but it makes sense to model them here, they will be needed for any sort of procedural build step. This results in the following fields being relevant for inclusions and exclusion: * `pyproject.toml` (always included in the source dist) * project.readme: PEP 621 * project.license-files: PEP 639 * module_root: `Path` * source_include: `Vec<Glob>` * source_exclude: `Vec<Glob>` * wheel_exclude: `Vec<Glob>` * data: `Map<KnownDataName, Path>` An opinionated choice is that that wheel excludes always contain the source excludes: Otherwise you could have a path A in the source tree that gets included when building the wheel directly from the source tree, but not when going through the source dist as intermediary, because A is in source excludes, but not in the wheel excludes. This has been a source of errors previously. In the process, I fixed a bug where we would skip directories and only include the files and were missing license due to absolute globs.	2024-12-01 11:32:35 +00:00
Charlie Marsh	8126a5ed32	Make MarkerTree Copy (#9542) ... ## Summary It's just a `usize`. It seems simpler and perhaps even more performant (?) to make it `Copy`.	2024-11-30 14:07:07 -05:00
Charlie Marsh	6bebf79ac3	Remove uses of Option<MarkerTreeContents> in PubGrubPackage (#9541) ... ## Summary Just use `MarkerTree::TRUE` instead of `None`.	2024-11-30 10:36:18 -05:00
Charlie Marsh	22fd9f7ff1	Pass extra when evaluating lockfile markers (#9539) ... ## Summary When we serialize and deserialize the lockfile, we remove the conflict markers. So in the linked case, the edges for the `tqdm` entries are like: ``` complexified_marker: UniversalMarker { pep508_marker: python_full_version >= '3.9.0', conflict_marker: true, }, ``` However... when we evaluate in-memory, the conflict markers are still there... ``` complexified_marker: UniversalMarker { pep508_marker: true, conflict_marker: extra == 't1' and extra != 't2', }, ``` So if `uv run` creates the lockfile, we evaluate this as `false`. We should make this consistent, and I expect @BurntSushi is aware. But for now, it's reasonable / correct to pass the extra when evaluating at this specific point, since we know the dependency was enabled by the marker. Closes https://github.com/astral-sh/uv/issues/9533#issuecomment-2508908591.	2024-11-30 14:22:18 +00:00
Charlie Marsh	53fe301b1d	Avoid using IDs across PubGrub states (#9538) ... ## Summary This isn't safe, because the prefetcher is global but the IDs could come from different PubGrub states (i.e., different forks).	2024-11-30 13:59:21 +00:00
Charlie Marsh	2aca623691	Remove unused specifier field from PubGrub structs (#9536)	2024-11-30 03:59:34 +00:00
Charlie Marsh	69811837e5	Support recursive extras with marker in pip compile -r pyproject.toml (#9535) ... ## Summary Closes https://github.com/astral-sh/uv/issues/9530.	2024-11-30 03:40:22 +00:00
Nathan McDougall	891e02d586	Add missing word to docs for run.md (#9527) ... ## Summary I found this sentence didn't read quite right without this "the". ## Test Plan No tests, docs-only change.	2024-11-29 21:58:20 -05:00
Charlie Marsh	950855877a	Use constraints in trace rather than irrelevant requires-python (#9529)	2024-11-29 19:25:43 +00:00
Charlie Marsh	58cf93a219	Un-gate --emit-marker-expression tests via --python-platform (#9528) ... These are tedious to update on non-Linux, but I think we can just use `--python-platform` to make them work on all platforms.	2024-11-29 19:23:12 +00:00
trag1c	9864d23f48	docs: correct wording for multiple sources section (#9504) ... ## Summary Corrects calling tags "commits". ## Test Plan N/A	2024-11-29 12:33:08 -05:00
konsti	772251027e	Make pip install snapshot independent of settings fields (#9522) ... When changing something about the settings, `invalid_pyproject_toml_option_unknown_field` would fail unexpectedly because the exact list of possible options had changed. Since we're already testing this list in the settings-related test `resolve_config_file`, i'm stubbing the exact output here.	2024-11-29 12:32:47 -05:00
Charlie Marsh	57900f33bd	Override manylinux_compatible with --python-platform (#9526) ... ## Summary Closes https://github.com/astral-sh/uv/issues/9521.	2024-11-29 17:26:24 +00:00
Jp	b9740d4e16	Align tempfile workspace dependencies with root project (#9524) ... <!-- 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 While working on potential bug fixes with temporary files on Windows (I think I am currently ecountering the same issue as #2810) I noticed that sub-workspaces were not all having the same `tempfile` version. And they were not relying on the cargo root project dependency. I don't know at all if it was done on purpose or not. (I also wanted to override the root dependency with a local source but it was not possible due to sub-workspaces not relying on the same). The root lockfile already pinned to the `3.14.0`. Some sub-workspaces were depending on the `3.12.0`, some others on the `3.14.0`. So I updated the root `Cargo.toml` to the `3.14.0`. Feel free to decline if it was done on purpose! No worries at all 🙂 Thanks! <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan All units tests are still passing on my side. Let's see with the pull-request CI 😄	2024-11-29 12:05:10 -05:00
Charlie Marsh	cf20673197	Upgrade to Rust 1.83 (#9511) ... ## Summary A lot of good new lints, and most importantly, error stabilizations. I tried to find a few usages of the new stabilizations, but I'm sure there are more. IIUC, this _does_ require bumping our MSRV.	2024-11-29 12:04:22 -05:00
konsti	b9b37a9bab	Build backend: Warn when visiting over 10k files (#9523) ... Also log how many files we visited in total as a debugging aid. No test for this one since we don't want to create 10k on disk in our test suite.	2024-11-29 16:46:11 +01:00
Charlie Marsh	590294a0ac	Propagate markers for recursive extras in resolver (#9509) ... ## Summary Closes https://github.com/astral-sh/uv/issues/9499#issuecomment-2506491209.	2024-11-28 12:40:00 -05:00
Zanie Blue	4a074141b6	Fixup version in prior uninstall instructions (#9485)	2024-11-28 08:00:09 -06:00
konsti	b80bd87b99	Don't emit unpinned warning for proxy packages (#9497) ... Whenever we see an unpinned proxy package, we know that its base package is also unpinned and emitted a warning. Part 1 of 2 for #8155	2024-11-28 12:39:38 +00:00
Charlie Marsh	8a27d4d340	Allow file: URLs to include package names (#9493) ... ## Summary Closes https://github.com/astral-sh/uv/issues/9489.	2024-11-27 22:27:07 -05:00
Zanie Blue	be651ed32d	Fix typo in entry point docs (#9491)	2024-11-28 02:48:52 +00:00
Charlie Marsh	201dfef780	Insert backslash when appending to system drive (#9488) ... ## Summary When you pass a system drive to `Path::join`, Rust doesn't insert a backslash between the drive and the path itself, so our lookups for system configuration were failing. Closes https://github.com/astral-sh/uv/issues/9416.	2024-11-27 19:38:29 -05:00
thirtysix	aa688226aa	Fix --refresh-package flag mentioned as --refresh-dependency (#9486) ... ## Summary This PR fixes name of `--refresh-package` flag in cache docs. It's misspelled as `--refresh-dependency`. ## Test Plan Deployed docs locally.	2024-11-27 17:14:01 -06:00
Charlie Marsh	f1ccbcb065	Consistently enforce requested-vs.-built metadata when retrieving wheels (#9484) ... ## Summary We were missing a bunch of edge cases, e.g., the wheel exists in the cache already. Closes https://github.com/astral-sh/uv/issues/9480.	2024-11-27 16:51:01 -05:00
Charlie Marsh	4f2b30ca02	Improve error messages for mismatches in tool.uv.sources (#9482) ... ## Summary Closes https://github.com/astral-sh/uv/issues/9479.	2024-11-27 20:10:39 +00:00
konsti	0b0d0f44f8	Publish: Warn when keyring has no password (#8827) ... When trying to upload without a password but with the keyring, check that the keyring has a password for the upload URL and username and warn if it doesn't. Fixes #8781	2024-11-27 20:54:49 +01:00
Charlie Marsh	68e3228f2b	Remove lxml from lock test (#9481) ... ## Summary Closes https://github.com/astral-sh/uv/issues/9467.	2024-11-27 18:39:38 +00:00
Zanie Blue	95cd8b8b3f	Bump version to 0.5.5 (#9478)	2024-11-27 11:37:39 -06:00
Zanie Blue	7df3ae2585	Add Python implementation example to limited resolution environments docs (#9475) ... Closes https://github.com/astral-sh/uv/issues/9473	2024-11-27 09:53:39 -06:00
Zanie Blue	6afb34091c	Expand entry points documentation (#9329)	2024-11-27 09:53:07 -06:00
Andrew Gallant	cc6bfa14d1	uv/tests: move conflicts tests to its own file ... There are already a fair number and I'm planning to add more. And `lock.rs` is already quite big. There aren't any new tests or other changes here. This is just moving tests and trimming down the function names to avoid redundancy in the names.	2024-11-27 10:51:11 -05:00
Charlie Marsh	ee84620e90	Use consistent formatting for build system errors (#9340) ... ## Summary These look pretty different from the help / hint messages we show on resolver failure. I've added color, backticks, and a "hint:" prefix. Before:  After: 	2024-11-27 14:22:53 +00:00
Charlie Marsh	0cd9c542ad	Show an interpreter-focused message for --target and --prefix (#9373) ... ## Summary With `uv pip install --target` and `--prefix`, we (1) should allow managed Pythons, and (2) should show a different message that's focused on the interpreter we selected, rather than the environment.	2024-11-27 14:21:46 +00:00
Charlie Marsh	7169b2c427	Respect sources in overrides and constraints (#9455) ... ## Summary We still only respect overrides and constraints in the workspace root -- which we may want to change -- but overrides and constraints are now correctly lowered. Closes https://github.com/astral-sh/uv/issues/8148.	2024-11-27 13:56:14 +00:00
konsti	8c8a1f071c	Fix tool.uv.dependency-metadata.[].version schema (#9468) ... Fixes #9443	2024-11-27 13:26:03 +00:00
Zanie Blue	b503a25556	Avoid filtering Python executables names during install tests (#9458) ... These were erroneously being filtered, interfering with the snapshots in #8650	2024-11-27 01:34:39 +00:00
konsti	8074917449	Upload: All metadata incl. PEP 639 (#9442) ... We were previously not uploading all metadata in the formdata of an upload request in the legacy api. Notably, we were missing the PEP 639 license-files field. I had to switch to pdm due to https://github.com/pypa/hatch/issues/1828	2024-11-27 00:25:08 +01:00
Zanie Blue	ba94d85d36	Allow disabling (most of) CI with no-test label (#9456)	2024-11-26 17:16:08 -06:00
Charlie Marsh	2534156eff	Use rich diagnostics for build failures (#9335) ... ## Summary Closes https://github.com/astral-sh/uv/issues/9323.	2024-11-26 15:05:59 -05:00
Charlie Marsh	916d5d7778	Migrate to PubGrub's arena for package names (#9448) ... ## Summary There's more we can do here, i.e., to leverage the IDs more widely, but this is a start.	2024-11-26 15:05:39 -05:00
Charlie Marsh	8aeaf98f59	Rename from Lowered to Canonical (#9447) ... By request: https://github.com/astral-sh/uv/pull/9341#pullrequestreview-2460979421.	2024-11-26 13:34:43 -05:00
Zanie Blue	7a0a5a806d	Update the dependencies documentation (#9359) ... This is a first-pass at updating the "Managing dependencies" page after moving some of the project concept documentation into it. I want to do more things, like improve visibility into upgrading packages and reordering some sections, but will tackle those separately for review. The primary goals here were to consolidate redundant information on dependency tables and improve the consistency of examples.	2024-11-26 12:32:56 -06:00
Zanie Blue	de84a897a1	Add dedicated error message for musl install attempts (#9430) ... Until https://github.com/astral-sh/uv/issues/6890 is fixed, it seems nice to explain that we do not support it rather than the generic message in https://github.com/astral-sh/uv/issues/9428	2024-11-26 12:30:07 -06:00
konsti	c94777fc54	Initialize rayon lazily (#9435) ... When performing a noop sync, we don't need the rayon threadpool, yet we pay for its initialization:  Be making the initialization lazy, we avoid that cost:  This code runs every time before user code in `uv run`. This means that before calling rayon, one now needs to call `LazyLock::force(&RAYON_INITIALIZE);`. Performance mode (CPU 0 is a perf core): ``` $ taskset -c 0 hyperfine --warmup 5 -N "/home/konsti/projects/uv/uv-main sync" "/home/konsti/projects/uv/target/profiling/uv sync" Benchmark 1: /home/konsti/projects/uv/uv-main sync Time (mean ± σ): 4.5 ms ± 0.1 ms [User: 2.7 ms, System: 1.8 ms] Range (min … max): 4.4 ms … 6.4 ms 640 runs Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options. Benchmark 2: /home/konsti/projects/uv/target/profiling/uv sync Time (mean ± σ): 4.4 ms ± 0.1 ms [User: 2.7 ms, System: 1.6 ms] Range (min … max): 4.3 ms … 5.0 ms 679 runs Summary /home/konsti/projects/uv/target/profiling/uv sync ran 1.03 ± 0.04 times faster than /home/konsti/projects/uv/uv-main sync ``` Power saver mode: ``` $ hyperfine --warmup 5 -N "/home/konsti/projects/uv/uv-main sync" "/home/konsti/projects/uv/target/profiling/uv sync" Benchmark 1: /home/konsti/projects/uv/uv-main sync Time (mean ± σ): 28.1 ms ± 1.2 ms [User: 15.5 ms, System: 20.3 ms] Range (min … max): 25.7 ms … 31.9 ms 102 runs Benchmark 2: /home/konsti/projects/uv/target/profiling/uv sync Time (mean ± σ): 24.0 ms ± 1.2 ms [User: 13.8 ms, System: 9.9 ms] Range (min … max): 22.2 ms … 28.2 ms 122 runs Summary /home/konsti/projects/uv/target/profiling/uv sync ran 1.17 ± 0.08 times faster than /home/konsti/projects/uv/uv-main sync ```	2024-11-26 14:58:38 +00:00
Charlie Marsh	edcff575f0	Treat less compatible tags as lower priority in resolver (#9339) ... ## Summary This is a second pass at https://github.com/astral-sh/uv/pull/7556, which was reverted in https://github.com/astral-sh/uv/pull/7608 due to a regression in https://github.com/astral-sh/uv/issues/7606. The behavior is actually correct, but a package (`nmslib`) publishes inconsistent metadata, and the change here happened to cause us to select a wheel with "wrong" metadata. It's arbitrary, but it did cause a regression for folks. Since we're now seeing other issues caused by the wrongness here (and since the reporter in https://github.com/astral-sh/uv/issues/7606 has since removed the dependency), I'm inclined to ship this fix. Closes https://github.com/astral-sh/uv/issues/7553. Closes https://github.com/astral-sh/uv/issues/9283.	2024-11-26 14:51:32 +00:00
Charlie Marsh	d18753527f	Remove python_version from lowered marker representation (#9343) ... ## Summary We never construct these -- they should be impossible, since we always translate to `python_full_version`. This PR encodes that impossibility in the types.	2024-11-26 14:39:36 +00:00
Charlie Marsh	df844e1ec9	Treat deprecated aliases as equivalent in marker algebra (#9342) ... ## Summary This PR modifies our lowered representation such that any deprecated aliases are treated as "the same" marker in the algebra. So, for example, we now recognize that this is impossible, despite the marker names being different: ``` typing-extensions ; platform.python_implementation == 'CPython' and python_implementation != 'CPython' ``` Similarly, we now recognize that this is just `sys_platform == 'win32'`, despite the presence of both markers: ``` anyio ; sys_platform == 'win32' and sys.platform == 'win32' ```	2024-11-26 14:27:24 +00:00
Charlie Marsh	106863069d	Report marker diagnostics during parsing, rather than evaluation (#9338) ... ## Summary I want to move towards a more normalized marker representation within the marker tree, which means that the things we warn against will disappear by the time we get to evaluation. I think it makes more sense to show these warnings when we create the tree, rather than when we evaluate it.	2024-11-26 14:15:33 +00:00
konsti	f886d08094	Make pytest output column width independent (#9436) ... Fixes #9336	2024-11-26 10:59:04 +01:00