Skip to content
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 sync should install dependency of all workspace members? #6874

Closed
jpambrun-vida opened this issue Aug 30, 2024 · 2 comments
Closed

uv sync should install dependency of all workspace members? #6874

jpambrun-vida opened this issue Aug 30, 2024 · 2 comments
Labels
question Asking for clarification or support

Comments

@jpambrun-vida
Copy link

Prior to 0.4.0 I had a [project]-less top level pyproject.toml in my workspace. I liked that uv sync would install the union of all workspace members dependencies as well as top level dev-dependencies. This gave me a great DX with code completion/types/tests etc in all modules.

Now I was following the release note recommendation of adding a top level [project] table, but can't seem to get that behavior again.

  • uv sync only installs top level dependencies
  • if I add all workspace modules as dependency in the top level it works in dev, but later in CI building with --package moduleA I get errors that it can't find say moduleB since I only copy the needed modules in the docker context (to avoid rebuilding a module if changes were only in an unrelated modules).

If there a way to get uv sync to install all dependencies from all members uv can find without specifying them explicitly? like it does when [project] isn't present? Or, will the current [project]-less behavior remain unchanged?

@charliermarsh
Copy link
Member

...but later in CI building with --package moduleA I get errors that it can't find say moduleB since I only copy the needed modules in the docker context (to avoid rebuilding a module if changes were only in an unrelated modules).

Are you looking for something like --no-install-workspace, to do a sync prior to copying over the code? It seems correct that --package root would fail if it depends on member and member doesn't exist.

@charliermarsh charliermarsh added the question Asking for clarification or support label Sep 1, 2024
@charliermarsh charliermarsh closed this as not planned Won't fix, can't repro, duplicate, stale Sep 3, 2024
@charliermarsh
Copy link
Member

Closing based on my reply but happy to follow-up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Asking for clarification or support
Projects
None yet
Development

No branches or pull requests

2 participants