Better warning for no direct build by konstin · Pull Request #15898 · astral-sh/uv

konstin · 2025-09-16T17:13:12Z

Setup

$ git clone https://github.com/wheelnext/variant_aarch64
$ cd variant_aarch64
$ git checkout 1d047e667dbce4c74878a68c653a6b41bc3d3684

Before

$ uv build -v
[...]
DEBUG Not using uv build backend direct build of , no pyproject.toml: TOML parse error at line 5, column 1
  |
5 | [project]
  | ^^^^^^^^^
missing field `version`
[...]

After

$ uv build -v
[...]
DEBUG Not using uv build backend direct build of ``, pyproject.toml does not match: The value for `build_system.build-backend` should be `"uv_build"`, not `"flit_core.buildapi"`
[...]

The empty string gets fixed in #15897

**Setup** ``` $ git clone https://github.com/wheelnext/variant_aarch64 $ cd variant_aarch64 $ git checkout 1d047e667dbce4c74878a68c653a6b41bc3d3684 ``` **Before** ``` $ uv build -v [...] DEBUG Not using uv build backend direct build of , no pyproject.toml: TOML parse error at line 5, column 1 | 5 | [project] | ^^^^^^^^^ missing field `version` [...] ``` **After** ``` $ uv build -v [...] DEBUG Not using uv build backend direct build of ``, pyproject.toml does not match: The value for `build_system.build-backend` should be `"uv_build"`, not `"flit_core.buildapi"` [...] ``` The empty string gets fixed in #15897

zanieb · 2025-09-16T17:39:56Z

Is there a reason it's hard to write a snapshot test for?

zanieb · 2025-09-16T17:40:12Z

Oh, it's a debug log.

konstin · 2025-09-16T17:41:25Z

I came across this when debugging a variant provider and the debug log led me to first believe the provider was broken, which wasn't the case.

zanieb · 2025-09-16T17:51:05Z

crates/uv-build-backend/src/metadata.rs

            Err(err) => {
                debug!(
-                    "Not using uv build backend direct build of {name}, no pyproject.toml: {err}"
+                    "Not using uv build backend direct build of `{name}`, \


Maybe?

Suggested change

"Not using uv build backend direct build of `{name}`, \

"Not using uv build backend direct build for source tree `{name}`, \

Separately, should we just use the unsimplified display here? A relative path doesn't seem super userful?

I'm not generally opposed it's just that we're using the user display everywhere already, so if we only change it here we'd get different displays in different locations.

We do use the other display in some other debug level logs. I don't have strong feelings.

Co-authored-by: Zanie Blue <[email protected]>

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [astral-sh/uv](https://github.com/astral-sh/uv) | patch | `0.8.17` -> `0.8.22` | 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 (astral-sh/uv)</summary> ### [`v0.8.22`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0822) [Compare Source](astral-sh/uv@0.8.21...0.8.22) Released on 2025-09-23. ##### Python - Upgrade Pyodide to 0.28.3 ([#15999](astral-sh/uv#15999)) ##### Security - Upgrade `astral-tokio-tar` to 0.5.5 which [hardens tar archive extraction](GHSA-3wgq-wrwc-vqmv) ([#16004](astral-sh/uv#16004)) ### [`v0.8.21`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0821) [Compare Source](astral-sh/uv@0.8.20...0.8.21) Released on 2025-09-23. ##### Enhancements - Refresh lockfile when `--refresh` is provided ([#15994](astral-sh/uv#15994)) ##### Preview features Add support for S3 request signing ([#15925](astral-sh/uv#15925)) ### [`v0.8.20`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0820) [Compare Source](astral-sh/uv@0.8.19...0.8.20) Released on 2025-09-22. ##### Enhancements - Add `--force` flag for `uv cache clean` ([#15992](astral-sh/uv#15992)) - Improve resolution errors with proxied packages ([#15200](astral-sh/uv#15200)) ##### Preview features - Allow upgrading pre-release versions of the same minor Python version ([#15959](astral-sh/uv#15959)) ##### Bug fixes - Hide `freethreaded+debug` Python downloads in `uv python list` ([#15985](astral-sh/uv#15985)) - Retain the cache lock and temporary caches during `uv run` and `uvx` ([#15990](astral-sh/uv#15990)) ##### Documentation - Add `package` level conflicts to the conflicting dependencies docs ([#15963](astral-sh/uv#15963)) - Document pyodide support ([#15962](astral-sh/uv#15962)) - Document support for free-threaded and debug Python versions ([#15961](astral-sh/uv#15961)) - Expand the contribution docs on issue selection ([#15966](astral-sh/uv#15966)) - Tweak title for viewing version in project guide ([#15964](astral-sh/uv#15964)) ### [`v0.8.19`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0819) [Compare Source](astral-sh/uv@0.8.18...0.8.19) Released on 2025-09-19. ##### Python - Add CPython 3.14.0rc3 - Upgrade OpenSSL to 3.5.3 See the [python-build-standalone release notes](https://github.com/astral-sh/python-build-standalone/releases/tag/20250918) for more details. ##### Bug fixes - Make `uv cache clean` parallel process safe ([#15888](astral-sh/uv#15888)) - Fix implied `platform_machine` marker for `win_arm64` platform tag ([#15921](astral-sh/uv#15921)) ### [`v0.8.18`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0818) [Compare Source](astral-sh/uv@0.8.17...0.8.18) Released on 2025-09-17. ##### Enhancements - Add PyG packages to torch backend ([#15911](astral-sh/uv#15911)) - Add handling for unnamed conda environments in base environment detection ([#15681](astral-sh/uv#15681)) - Allow selection of debug build interpreters ([#11520](astral-sh/uv#11520)) - Improve `uv init` defaults for native build backend cache keys ([#15705](astral-sh/uv#15705)) - Error when `pyproject.toml` target does not exist for dependency groups ([#15831](astral-sh/uv#15831)) - Infer check URL from publish URL when known ([#15886](astral-sh/uv#15886)) - Support Gitlab CI/CD as a trusted publisher ([#15583](astral-sh/uv#15583)) - Add GraalPy 25.0.0 with support for Python 3.12 ([#15900](astral-sh/uv#15900)) - Add `--no-clear` to `uv venv` to disable removal prompts ([#15795](astral-sh/uv#15795)) - Add conflict detection between `--only-group` and `--extra` flags ([#15788](astral-sh/uv#15788)) - Allow `[project]` to be missing from a `pyproject.toml` ([#14113](astral-sh/uv#14113)) - Always treat conda environments named `base` and `root` as base environments ([#15682](astral-sh/uv#15682)) - Improve log message when direct build for `uv_build` is skipped ([#15898](astral-sh/uv#15898)) - Log when the cache is disabled ([#15828](astral-sh/uv#15828)) - Show pyx organization name after authenticating ([#15823](astral-sh/uv#15823)) - Use `_CONDA_ROOT` to detect Conda base environments ([#15680](astral-sh/uv#15680)) - Include blake2b hash in `uv publish` upload form ([#15794](astral-sh/uv#15794)) - Fix misleading debug message when removing environments in `uv sync` ([#15881](astral-sh/uv#15881)) ##### Deprecations - Deprecate `tool.uv.dev-dependencies` ([#15469](astral-sh/uv#15469)) - Revert "feat(ci): build loongarch64 binaries in CI ([#15387](astral-sh/uv#15387))" ([#15820](astral-sh/uv#15820)) ##### Preview features - Propagate preview flag to client for `native-auth` feature ([#15872](astral-sh/uv#15872)) - Store native credentials for realms with the https scheme stripped ([#15879](astral-sh/uv#15879)) - Use the root index URL when retrieving credentials from the native store ([#15873](astral-sh/uv#15873)) ##### Bug fixes - Fix `uv sync --no-sources` not switching from editable to registry installations ([#15234](astral-sh/uv#15234)) - Avoid display of an empty string when a path is the working directory ([#15897](astral-sh/uv#15897)) - Allow cached environment reuse with `@latest` ([#15827](astral-sh/uv#15827)) - Allow escaping spaces in --env-file handling ([#15815](astral-sh/uv#15815)) - Avoid ANSI codes in debug! messages ([#15843](astral-sh/uv#15843)) - Improve BSD tag construction ([#15829](astral-sh/uv#15829)) - Include SHA when listing lockfile changes ([#15817](astral-sh/uv#15817)) - Invert the logic for determining if a path is a base conda environment ([#15679](astral-sh/uv#15679)) - Load credentials for explicit members when lowering ([#15844](astral-sh/uv#15844)) - Re-add `triton` as a torch backend package ([#15910](astral-sh/uv#15910)) - Respect `UV_INSECURE_NO_ZIP_VALIDATION=1` in duplicate header errors ([#15912](astral-sh/uv#15912)) ##### Documentation - Add GitHub Actions to PyPI trusted publishing example ([#15753](astral-sh/uv#15753)) - Add Coiled integration documentation ([#14430](astral-sh/uv#14430)) - Add verbose output to the getting help section ([#15915](astral-sh/uv#15915)) - Document `NO_PROXY` support ([#15816](astral-sh/uv#15816)) - Document cache-keys for native build backends ([#15811](astral-sh/uv#15811)) - Add documentation for dependency group `requires-python` ([#14282](astral-sh/uv#14282)) </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 the tracing Verbose output and debugging label Sep 16, 2025

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

konstin force-pushed the konsti/better-warning-for-no-direct-build branch from 5059bb6 to 14e57ca Compare September 16, 2025 17:17

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

Rustfmt

c5204cf

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

zanieb reviewed Sep 16, 2025

View reviewed changes

Update crates/uv-build-backend/src/metadata.rs

fe67b2f

Co-authored-by: Zanie Blue <[email protected]>

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

zanieb approved these changes Sep 17, 2025

View reviewed changes

konstin merged commit eb5ec95 into main Sep 17, 2025
98 checks passed

konstin deleted the konsti/better-warning-for-no-direct-build branch September 17, 2025 11:18

BrewTestBot mentioned this pull request Sep 17, 2025

uv 0.8.18 Homebrew/homebrew-core#244543

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

Better warning for no direct build#15898

Better warning for no direct build#15898
konstin merged 3 commits intomainfrom
konsti/better-warning-for-no-direct-build

konstin commented Sep 16, 2025

Uh oh!

zanieb commented Sep 16, 2025

Uh oh!

zanieb commented Sep 16, 2025

Uh oh!

konstin commented Sep 16, 2025

Uh oh!

zanieb Sep 16, 2025

Uh oh!

konstin Sep 17, 2025

Uh oh!

zanieb Sep 17, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	"Not using uv build backend direct build of `{name}`, \
	"Not using uv build backend direct build for source tree `{name}`, \

Comments

Conversation

konstin commented Sep 16, 2025

Uh oh!

zanieb commented Sep 16, 2025

Uh oh!

zanieb commented Sep 16, 2025

Uh oh!

konstin commented Sep 16, 2025

Uh oh!

zanieb Sep 16, 2025

Choose a reason for hiding this comment

Uh oh!

konstin Sep 17, 2025

Choose a reason for hiding this comment

Uh oh!

zanieb Sep 17, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants