Bump dask, distributed, fsspec versions
#201
Conversation
|
This version bump doesn't actually seem to work 😅 |
karlhigley
changed the title
dask, distributed, fsspec versions to >=2022.7.0dask, distributed, fsspec versions to ==2022.7.1
|
@jperez999 Seeing a bunch of errors like this in the Systems tests: Seems like maybe there's a chunk of code for either Core or NVT somewhere that didn't get pushed. Any idea if you have something stashed somewhere? EDIT: The relevant method is right here in |
@karlhigley I think the issue is that we're (edit: NOT) installing the dev version of NVTabular, and instead it's picking up the latest published version in pypi which doesn't have the |
requirements.txt
Outdated
| @@ -1,11 +1,11 @@ | |||
| dask>=2022.3.0 | |||
| distributed>=2022.3.0 | |||
| dask==2022.7.1 | |||
There was a problem hiding this comment.
Since this is going to turn into the package install_requires. having a range (minimum) may be preferable to the explicit pinned version here to improve the chances of finding compatibile versions of packages in a project?
There was a problem hiding this comment.
I had trouble with that because it ended up picking newer versions than we're actually compatible with, but I'm not sure where the cut-off is.
karlhigley
force-pushed
the
fix/io-deps
branch
from
222d0d7 to
a3474a1
Compare
karlhigley
changed the title
dask, distributed, fsspec versions to ==2022.7.1dask, distributed, fsspec versions
`fsspec 2022.8.1` got yanked and replaced with `2022.8.2`, so these are equivalent versions although the numbers are slightly different.
karlhigley
force-pushed
the
fix/io-deps
branch
from
a3474a1 to
46596e7
Compare
There's a breaking change in distributed 2022.11.1 that our version of `dask_cuda` isn't compatible with yet.
No description provided.