You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The README already shows how to use build with uv, but does so assuming someone's also using pipx.
Given that uv has functionality which overlaps with pipx, is it perhaps worth changing this section to assume someone is using uv's own functionality for installing build? (Doing so is not as simple as replacing pipx with uvx in the command, as build reiles on entry-points to tell pipx to invoke it via -m).
Specifically, is it worth changing that section to say:
uv run --with 'build[uv]' -m build --installer=uv
?
The text was updated successfully, but these errors were encountered:
I don't think the pipx invocation should be changed to uv's, but examples can be provided for both. If you're running build via uv, you don't need the uv extra, and the uvx invocation can be simplified to:
The README already shows how to use
build
withuv
, but does so assuming someone's also usingpipx
.Given that
uv
has functionality which overlaps withpipx
, is it perhaps worth changing this section to assume someone is usinguv
's own functionality for installingbuild
? (Doing so is not as simple as replacingpipx
withuvx
in the command, asbuild
reiles onentry-points
to tellpipx
to invoke it via-m
).Specifically, is it worth changing that section to say:
?
The text was updated successfully, but these errors were encountered: