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
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?
The text was updated successfully, but these errors were encountered:
...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.
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--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?The text was updated successfully, but these errors were encountered: