-
Notifications
You must be signed in to change notification settings - Fork 47
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
v0.2.6 broken due to updates in Dask #835
Comments
Thank you for reporting; we are going to release 0.2.7 soon, which as you observed will include the constraint for Dask. |
Same is happening to me, which is breaking all tests of a tool I am developing, and uses squidpy (therefore spatialdata too) as a requirement:
|
@earmingol I have made a release 3 days ago which adds a constraint for Dask when installing The problem is due to the fact that |
You can install Dask==2024.12.1 to your environment, which does seem to work with spatialdata 0.2.6 |
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.dataframeThis 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.
The text was updated successfully, but these errors were encountered: