Replies: 1 comment 1 reply
-
^^ where is this line? I'm actually not a big fan of dask.dataframe + import abbreviations so that doesn't look like a line I would write. Maybe it's a bug from another package like But pandas went through major api changes (v2.0) this year, so that probably caused this everywhere. Sounds like we need to just bump the minimum dask version in our CI. I can do that in #524 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working to merge the warrenapp into Simmate and I've been running into an error when running
simmate workflows explore
. The error I get seems to be caused by the following import:and throws the following error
There is a stack overflow discussion on this error (here) which seems to indicate that there's an incompatibility between some versions of dask and pandas. Checking my conda environment, I noticed that my dev install of simmate defaulted to dask 2023.1.1 and pandas 2.0.3. I'm not to familiar with how conda handles dependencies so I'm not sure what's making dask stay on this older version since Simmate seems to have the dependency set up to dask 2023.6.1. I used pip to force an update to dask 2023.6.1 and calling the command works fine now, but there should be some way to make sure a conda install of Simmate will function without having to do this. Maybe increase the dependency range in the pyproject.toml to something higher?
Any suggestions?
Full error is in the attached txt file.
dask pandas error.txt
Beta Was this translation helpful? Give feedback.
All reactions