mediumBackend

How do uv workspaces and named dependency groups work?

Q: How do uv workspaces and named dependency groups work?

`uv` workspaces (like Cargo) let one `uv.lock` manage multiple packages; `[dependency-groups]` and `tool.uv.sources` wire local path deps. Single uv.lock Many packages | | Without workspaces | With workspaces | |---|---|---| | Lockfiles | One per package, drift | One root `uv.lock` | | Local dep | `pip install -e ../lib` | `tool.uv.sources = {lib = {workspace=true}}` | | Sync | Per package | `uv sync` at root builds all | | Groups | `optional-dependencies` | `[dependency-groups] dev = [...]` | This replaces `poetry`

1.2k views

Understand the problem

Monorepo with uv's Cargo-like workspaces.

uvworkspacesmonorepo

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Nudge consolestandby

Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.

Study the solution

uv workspaces (like Cargo) let one uv.lock manage multiple packages; [dependency-groups] and tool.uv.sources wire local path deps.

Solution ready — 2 min read

Classified // press E to declassify

Join the discussion

Discussion (0)

No responses yet. Be the first to share what you think.

Transmission complete // awaiting log

KEEP THE
STREAK ALIVE.

Dossier 25 of 120 decoded in the Python track. One more won't hurt.

Back to track

Next up→

What is the difference between an iterable and an iterator?

Continue