v0.2.6 broken due to updates in Dask
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
NOTE: This can be easily solved by updating to v0.2.7-pre0, but I thought I would notify of the breaking change anyways.
Within the past hour of me posting this, the "dask" package posted a new 2025.1.0 release that removes some legacy dask support. In spatialdata==0.2.6 there is no specific version of dask specified in the pyproject.toml dependencies. If you try to run import spatialdata as sd it will error out with a message like "The legacy implementation is no longer supported" referring to dask.dataframe
This was fixed in the v0.2.7-pre0 tag, but I still think it would be a good idea to either have a notice somewhere that 0.2.6 will not work or backport the Dask dependency settings from the current pyproject.toml to v0.2.6.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the v0.2.6 release with the current pyproject.toml and the v0.2.7-pre0 tag, focusing on the Dask dependency settings. Confirm the import failure with the reported Dask release, then determine whether the release needs a backported dependency constraint or a notice that v0.2.6 is incompatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100