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 compatability #79

Draft
wants to merge 2 commits into
base: branch-25.02
Choose a base branch
from

Conversation

TomAugspurger
Copy link

@TomAugspurger TomAugspurger commented Jan 16, 2025

Follows the changes in dask/dataframe/accessor.py after https://github.com/dask/dask/pull/11606/files#diff-02020cca578450d377d1f45564123cfae3647b7f4435c55cd6b5ac41f1af2225

Closes #78

Edit: I'll get my commits signed and re-push.

Copy link

copy-pr-bot bot commented Jan 16, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@TomAugspurger TomAugspurger force-pushed the tom/fix/dask-2025.1-compat branch from 2664652 to 632166e Compare January 16, 2025 19:02
@@ -12,9 +12,9 @@ name = "rapids-dask-dependency"
version = "25.02.00a0"
description = "Dask and Distributed version pinning for RAPIDS"
dependencies = [
"dask==2024.12.1",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried briefly to support dask>=2025.12.1. It'd be relatively easy at the code level, by putting the imports and Accessor definition behind a Dask version check.

The packaging side is a bit tricker. dask-expr is pinned tightly to dask==2024.12.1: https://github.com/dask/dask-expr/blob/42e7a8958ba286a4c7b2f199d143a70b0b479489/pyproject.toml#L29C6-L29C23. Including dask-expr as a dependency will force the solver to pick 2024.12.1.

We could maybe resolve this with a new release of dask-expr that relaxes that pin and then depend on that. But I'm not sure how valuable this is, so I won't chase it right now.

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.

ImportError: cannot import name 'check_to_pydatetime_deprecation' from 'dask.dataframe._compat' on dask main
1 participant