Skip to content
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

dask 2025.1.0 compatibility #324

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

TomAugspurger
Copy link
Contributor

@TomAugspurger TomAugspurger commented Jan 11, 2025

This updates dask-geopandas to be compatible with the next release of
dask, which moves dask-expr into dask.dataframe.

I've dropped support for all older versions of dask. Only new versions,
based on dask-expr / with query planning, are supported.

dask currently supports Python>=3.10, so I've bumped that requirement as well.

Closes #324

This updates dask-geopandas to be compatible with the next release of
dask, which moves dask-expr into dask.dataframe.

I've dropped support for all older versions of dask. Only new versions,
based on dask-expr / with query planning, are supported.
@TomAugspurger
Copy link
Contributor Author

OK, the upstream-dev tests passed at https://github.com/geopandas/dask-geopandas/actions/runs/12734777705/job/35492743562?pr=324. The rest are failing because that's using a new dask.dataframe.api module that's present on main but not yet released. IMO, we can plan to release dask-geopandas the same day as dask 2025.1.0, and maintain compatibility without a ton of compatibility code.

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