-
Notifications
You must be signed in to change notification settings - Fork 45
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
Error when importing dask_geopandas.expr on Python 3.10 when Dask query planning is disabled #311
Comments
Thanks for the report. I'm... a bit confused about how that error is being hit. I'm not able to reproduce it with just this, and the traceback doesn't make a ton of sense: import dask
dask.config.set({'dataframe.query-planning': False})
import dask_geopandas.core
import dask_geopandas.expr relatedly, is datashader compatible with dask-expr? I'm guessing we'll require that soon-ish, given the limited maintenance bandwidth here. |
Have you tried with Python 3.10? I'm able to reproduce this with this set of dependencies. conda list
Yes, I believe compatibility with dask-expr has been achieved with datashader 0.16.1 and 0.16.2 (https://datashader.org/releases.html). |
I can reproduce it with a similar environment as you have above ( |
Searching online for the error, some comments point to this issue appearing when adding And indeed, it seems that slots were introduced (at least non-empty slots) in Downgrading dask to 2024.7, then the error goes away (although when upgrading dask in my dev env, I still cannot reproduce the error there, so it's not just the dask version that is in play .. Upgrading Python to 3.11 in the test env, then the error also goes away, so it's specific to Python 3.10?) |
Given that this only seems to happen for Python 3.10, when explicitly importing @maximlt what was the use case in datashader to explicitly import |
Thanks for digging into that :)
That's also my conclusion. It's part of an |
Would it be sufficient for datashader to just do |
The test runs of datashader have been failing recently on Python 3.10 and the issue can be narrowed down to this piece of code:
Traceback:
I just wanted to report it in case someone else stumbles upon that weird corner case, we're going to slightly modify datashader to deal with that case directly. Feel free to close the issue!
The text was updated successfully, but these errors were encountered: