-
Notifications
You must be signed in to change notification settings - Fork 698
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
"uv build --all" command not working? #8530
Comments
Interesting... this works as expected for me:
|
Oh, do your projects have a |
I'm going to add some error messages to fix this up. |
Nope they didn't have a
Yes, that would be great, in order to avoid confusion. Thanks for your help again, Charlie! |
I don't know if this is a bug or if I'm doing something wrong, but I can't get the
uv build --all
command to work.According to the
uv build --help
command, the--all
flag should build all packages in the workspace.$ uv build --help ... Options: --package <PACKAGE> Build a specific package in the workspace + --all Builds all packages in the workspace
I have a workspace with two packages,
lib1
andlib2
.In the root
pyproject.toml
, I have the following configuration to define the members of the workspace (I also tried specifying the path to each package individually, likemembers = ["packages/lib1", "packages/lib2"]
but it didn't work either):When I run
uv build --all
, the following error is raised:$ uv build --all error: No packages found in workspace
If I run
uv build --package lib1
, it works as expected, but we are forced to build each package individually.Is this a bug or am I missing something / misinterpreting what the
--all
flag is supposed to do?Thanks!
The text was updated successfully, but these errors were encountered: