Clarify no-build docs for editable requirements - #20234
Merged
Merged
Conversation
konstin
approved these changes
Jul 8, 2026
Member
|
FWIW, our current behavior is buggy, we should consider "first party"/local dependencies, not editable, there is no reason while this pass [project]
name = "foo"
version = "0.1.0"
requires-python = ">=3.14.0"
dependencies = ["bar"]
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
[tool.uv.workspace]
members = [
"bar",
]
[tool.uv.sources]
bar = { workspace = true, editable = true }while fails with |
Member
Author
|
Looks like that's #12607? |
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
--no-buildhelp says resolving will not run arbitrary Python code and operations that require building distributions will fail. This conflicts withdocs/pip/compatibility.mdand the implementation:--no-buildaliases--only-binary :all:, but uv may still build editable requirements under either option, and their build backends may execute arbitrary Python code.This PR updates the help text to align with reality and the doc mentioned above.