Skip to content

fix(deps): require dask[distributed] instead of bare dask - #6

Open
betolink wants to merge 1 commit into
mainfrom
fix/distributed-dep
Open

betolink wants to merge 1 commit into
mainfrom
fix/distributed-dep

Conversation

@betolink

Copy link
Copy Markdown
Member

A Coiled software environment built from the plugin was missing distributed, so worker startup failed with:

/opt/coiled/env/bin/python: Error while finding module specification for 'distributed.cli.dask_spec' (ModuleNotFoundError: No module named 'distributed')

client= is a core option and requires distributed; Coiled/remote clusters also need it in the worker environment. This makes it a core dependency instead of relying on the [distributed] extra.

  • core: dask → dask[distributed]
  • [distributed] extra: now only dask-labextension (the JupyterLab integration)

Verified: uv sync --locked --extra test --extra kerchunk + 115 tests + ruff.

`client=` runs the per-granule opens on a Dask cluster, and Coiled/remote
software environments need `distributed` present to start workers
(`distributed.cli.dask_spec`). Declaring it avoids environments that install
dask but not distributed.

The `distributed` extra now only adds `dask-labextension`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant