Warn when using `uv_build` settings without `uv_build` by konstin · Pull Request #15750 · astral-sh/uv

konstin · 2025-09-09T12:23:49Z

To help with cases such as #15655.

A question is when to show this warning. I've used sources as a proxy as URL dependencies with enabled sources are likely those controlled by the user, and they include workspace and git cloned path dependencies.

The first commit is a refactoring, the second commit the implementation.

Fixes #15740

konstin · 2025-09-12T14:14:32Z

crates/uv-build-frontend/src/lib.rs

+                "There are settings for the `uv_build` build backend defined in \
+                `tool.uv.build-backend`, but the project does not use the `uv_build` backend: {}",


One potential drawback is that we assume that all future versions will have build-system = "uv_build".

zsol

I've been wanting to make this refactor for a while now

zanieb · 2025-09-16T15:53:04Z

crates/uv/tests/it/build_backend.rs

+    warning: There are settings for the `uv_build` build backend defined in `tool.uv.build-backend`, but the project does not use the `uv_build` backend: [TEMP_DIR]/pyproject.toml
+    Building wheel from source distribution...
+    warning: There are settings for the `uv_build` build backend defined in `tool.uv.build-backend`, but the project does not use the `uv_build` backend: [CACHE_DIR]/sdists-v9/[TMP]/pyproject.toml


Can we avoid warning multiple times here?

I need to figure our something that works despite the different paths

I've removed the path, it's clearer this was got Git dependencies too.

crates/uv/tests/it/build_backend.rs

zanieb · 2025-09-16T15:54:53Z

crates/uv/tests/it/build_backend.rs

+
+    ----- stderr -----
+    Building source distribution...
+    warning: There are settings for the `uv_build` build backend defined in `tool.uv.build-backend`, but the project does not use the `uv_build` backend: [TEMP_DIR]/pyproject.toml


We might want to rephrase so it's clearer what we're referring to at the end, e.g., "but the uv_build backend is not used by the project at: PATH"

zanieb · 2025-12-03T13:09:20Z

crates/uv-build-frontend/src/lib.rs

+            // Show name/version where available to avoid showing a (duplicate) warning with
+            // a temporary path.


(I'm not sure I'd understand this comment without the context from this pull request review)

zanieb · 2025-12-03T13:12:56Z

crates/uv/tests/it/build_backend.rs

+
+    ----- stderr -----
+    Building source distribution...
+    warning: `pyproject.toml` of project==0.1.0 defines settings for `uv_build` in `tool.uv.build-backend`, but does not use `uv_build`


Does it make sense to say "pyproject.toml of"? Isn't that the only place it can be defined?

Does it make sense to say the version? If it's first-party, isn't the version just noise? (and it's present in the built file name too if really helpful).

I think I'd be confused about what it means that it doesn't use uv_build, maybe it'd help to show the other backend?

I think I might say

project-name defines settings for uv_build in tool.uv.build-backend, but does not use uv_build ()

where <hint> is like

(no build-system is defined)

or

(build-system uses hatchling)

I've updated the hint to show only the package name and also show the actual build backend

konstin · 2026-02-20T14:27:19Z

crates/uv-build-frontend/src/lib.rs

-            Err(err) => Err(Box::new(err.into())),
        }
+
+        let backend = if let Some(build_system) = pyproject_toml.build_system {


This code only moved.

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [uv](https://github.com/astral-sh/uv) | patch | `0.10.7` → `0.10.9` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>astral-sh/uv (uv)</summary> ### [`v0.10.9`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0109) [Compare Source](astral-sh/uv@0.10.8...0.10.9) Released on 2026-03-06. ##### Enhancements - Add `fbgemm-gpu`, `fbgemm-gpu-genai`, `torchrec`, and `torchtune` to the PyTorch list ([#18338](astral-sh/uv#18338)) - Add torchcodec to PyTorch List ([#18336](astral-sh/uv#18336)) - Log the duration we took before erroring ([#18231](astral-sh/uv#18231)) - Warn when using `uv_build` settings without `uv_build` ([#15750](astral-sh/uv#15750)) - Add fallback to `/usr/lib/os-release` on Linux system lookup failure ([#18349](astral-sh/uv#18349)) - Use `cargo auditable` to include SBOM in uv builds ([#18276](astral-sh/uv#18276)) ##### Configuration - Add an environment variable for `UV_VENV_RELOCATABLE` ([#18331](astral-sh/uv#18331)) ##### Performance - Avoid toml `Document` overhead ([#18306](astral-sh/uv#18306)) - Use a single global workspace cache ([#18307](astral-sh/uv#18307)) ##### Bug fixes - Continue on trampoline job assignment failures ([#18291](astral-sh/uv#18291)) - Handle the hard link limit gracefully instead of failing ([#17699](astral-sh/uv#17699)) - Respect build constraints for workspace members ([#18350](astral-sh/uv#18350)) - Revalidate editables and other dependencies in scripts ([#18328](astral-sh/uv#18328)) - Support Python 3.13+ on Android ([#18301](astral-sh/uv#18301)) - Support `cp3-none-any` ([#17064](astral-sh/uv#17064)) - Skip tool environments with broken links to Python on Windows ([#17176](astral-sh/uv#17176)) ##### Documentation - Add documentation for common marker values ([#18327](astral-sh/uv#18327)) - Improve documentation on virtual dependencies ([#18346](astral-sh/uv#18346)) ### [`v0.10.8`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0108) [Compare Source](astral-sh/uv@0.10.7...0.10.8) Released on 2026-03-03. ##### Python - Add CPython 3.10.20 - Add CPython 3.11.15 - Add CPython 3.12.13 ##### Enhancements - Add Docker images based on Docker Hardened Images ([#18247](astral-sh/uv#18247)) - Add resolver hint when `--exclude-newer` filters out all versions of a package ([#18217](astral-sh/uv#18217)) - Configure a real retry minimum delay of 1s ([#18201](astral-sh/uv#18201)) - Expand `uv_build` direct build compatibility ([#17902](astral-sh/uv#17902)) - Fetch CPython from an Astral mirror by default ([#18207](astral-sh/uv#18207)) - Download uv releases from an Astral mirror in installers by default ([#18191](astral-sh/uv#18191)) - Add SBOM attestations to Docker images ([#18252](astral-sh/uv#18252)) - Improve hint for installing meson-python when missing as build backend ([#15826](astral-sh/uv#15826)) ##### Configuration - Add `UV_INIT_BARE` environment variable for `uv init` ([#18210](astral-sh/uv#18210)) ##### Bug fixes - Prevent `uv tool upgrade` from installing excluded dependencies ([#18022](astral-sh/uv#18022)) - Promote authentication policy when saving tool receipts ([#18246](astral-sh/uv#18246)) - Respect exclusions in scripts ([#18269](astral-sh/uv#18269)) - Retain default-branch Git SHAs in `pylock.toml` files ([#18227](astral-sh/uv#18227)) - Skip installed Python check for URL dependencies ([#18211](astral-sh/uv#18211)) - Respect constraints during `--upgrade` ([#18226](astral-sh/uv#18226)) - Fix `uv tree` orphaned roots and premature deduplication ([#17212](astral-sh/uv#17212)) ##### Documentation - Mention cooldown and tweak inline script metadata in dependency bots documentation ([#18230](astral-sh/uv#18230)) - Move cache prune in GitLab to `after_script` ([#18206](astral-sh/uv#18206)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

konstin added error messages Messaging when something goes wrong build-backend labels Sep 9, 2025

konstin temporarily deployed to uv-test-registries September 9, 2025 12:26 — with GitHub Actions Inactive

konstin commented Sep 12, 2025

View reviewed changes

konstin force-pushed the konsti/warn-on-unused-build-backend-settings branch from fad531f to 0226753 Compare September 16, 2025 10:19

konstin temporarily deployed to uv-test-registries September 16, 2025 10:21 — with GitHub Actions Inactive

zsol approved these changes Sep 16, 2025

View reviewed changes

zanieb reviewed Sep 16, 2025

View reviewed changes

crates/uv/tests/it/build_backend.rs Outdated Show resolved Hide resolved

zanieb reviewed Sep 16, 2025

View reviewed changes

konstin temporarily deployed to uv-test-registries September 16, 2025 16:17 — with GitHub Actions Inactive

konstin temporarily deployed to uv-test-registries September 17, 2025 10:52 — with GitHub Actions Inactive

konstin force-pushed the konsti/warn-on-unused-build-backend-settings branch from 44c9302 to a7d14f7 Compare October 9, 2025 13:39

konstin temporarily deployed to uv-test-registries October 9, 2025 13:42 — with GitHub Actions Inactive

This comment was marked as off-topic.

Sign in to view

konstin force-pushed the konsti/warn-on-unused-build-backend-settings branch from a7d14f7 to 9c5cf83 Compare November 24, 2025 10:11

konstin temporarily deployed to uv-test-registries November 24, 2025 10:13 — with GitHub Actions Inactive

konstin mentioned this pull request Dec 2, 2025

Noisily allow redundant entries in tool.uv.build-backend.module-name #16928

Merged

This was referenced Dec 3, 2025

Refactor uv_build warning handling #16961

Open

Consider making the uv_build warning heuristic more precise #16962

Open

zanieb reviewed Dec 3, 2025

View reviewed changes

konstin force-pushed the konsti/warn-on-unused-build-backend-settings branch from 9c5cf83 to 1975616 Compare December 11, 2025 14:42

konstin temporarily deployed to uv-test-registries December 11, 2025 14:46 — with GitHub Actions Inactive

konstin mentioned this pull request Feb 20, 2026

option to specify a project root directory to be added to the python path #11175

Open

konstin force-pushed the konsti/warn-on-unused-build-backend-settings branch from 1975616 to 0912eea Compare February 20, 2026 14:26

konstin commented Feb 20, 2026

View reviewed changes

Warn when using uv_build settings without uv_build

bb4e82e

konstin force-pushed the konsti/warn-on-unused-build-backend-settings branch from 0912eea to bb4e82e Compare February 20, 2026 14:40

zanieb approved these changes Mar 5, 2026

View reviewed changes

zanieb merged commit 87b2539 into main Mar 5, 2026
53 checks passed

zanieb deleted the konsti/warn-on-unused-build-backend-settings branch March 5, 2026 12:56

BrewTestBot mentioned this pull request Mar 7, 2026

uv 0.10.9 Homebrew/homebrew-core#271033

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Warn when using `uv_build` settings without `uv_build`#15750

Warn when using `uv_build` settings without `uv_build`#15750
zanieb merged 1 commit intomainfrom
konsti/warn-on-unused-build-backend-settings

konstin commented Sep 9, 2025

Uh oh!

konstin Sep 12, 2025

Uh oh!

zsol left a comment

Uh oh!

zanieb Sep 16, 2025

Uh oh!

konstin Sep 17, 2025

Uh oh!

konstin Nov 24, 2025

Uh oh!

Uh oh!

zanieb Sep 16, 2025 •

edited

Loading

Uh oh!

This comment was marked as off-topic.

zanieb Dec 3, 2025

Uh oh!

zanieb Dec 3, 2025

Uh oh!

konstin Dec 11, 2025

Uh oh!

konstin Feb 20, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

		"There are settings for the `uv_build` build backend defined in \
		`tool.uv.build-backend`, but the project does not use the `uv_build` backend: {}",

		// Show name/version where available to avoid showing a (duplicate) warning with
		// a temporary path.

Conversation

konstin commented Sep 9, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

zsol left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

zanieb Sep 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This comment was marked as off-topic.

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

zanieb Sep 16, 2025 •

edited

Loading