-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove build backend parking breaks #11576
base: main
Are you sure you want to change the base?
Conversation
We want to make it easier for users to try the build backend, so we add `UV_PREVIEW=1`
much appreciated! |
__all__ = [ | ||
"find_uv_bin", | ||
# PEP 517 hook `build_sdist`. | ||
"build_sdist", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this preclude us from moving these into a separate namespace later? (as discussed elsewhere)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
def warn_config_settings(config_settings: "Mapping[Any, Any] | None" = None) -> None: | ||
import os | ||
import sys | ||
|
||
if not os.environ.get("UV_PREVIEW"): | ||
print( | ||
"Warning: The uv build backend is in preview. " | ||
"Set the `UV_PREVIEW` environment variable to `1` to acknowledge.", | ||
file=sys.stderr, | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's kind of weird to have this in warn_config_settings
?
We want to make it easier for users to try the build backend, so we allow using the build backend without requiring
UV_PREVIEW=1
. Instead, we only print a note about the preview status of the build backend. This improves using packages with the uv build backend with other PEP 517 frontends that don't have uv's--preview
flag.