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-CUDA 23.12.0 requires rapids-dask-dependency on PyPI #1297

Closed
jakirkham opened this issue Dec 9, 2023 · 2 comments
Closed

Dask-CUDA 23.12.0 requires rapids-dask-dependency on PyPI #1297

jakirkham opened this issue Dec 9, 2023 · 2 comments

Comments

@jakirkham
Copy link
Member

jakirkham commented Dec 9, 2023

Recently some changes were made to dask-cuda packages to depend on rapids-dask-dependency ( #1270 ) to make managing the Dask dependency easier

The recently released sdist and whl on PyPI of dask-cuda for 23.12 require rapids-dask-dependency. However it looks like there is not a 23.12 release of rapids-dask-dependency yet. Raised upstream issue ( rapidsai/rapids-dask-dependency#12 ) to follow-up

Am unsure whether to expect this at this stage (we are in the midst of the 23.12 release) or if there is some issue/bug that we need to dig into further

For now am filing this to track as well as let other users know this doesn't work yet (should they bump into it as well)

@vyasr
Copy link
Contributor

vyasr commented Dec 12, 2023

Up until this release dask-cuda was publishing both nightlies and final releases directly to PyPI on its own independently of the rest of RAPIDS. In the future, dask-cuda nightlies will be published to our nightly index instead, and we'll go through our internal processes for getting the final releases uploaded to PyPI. That matches what we'll be doing for rapids-dask-dependency, so the timelines will be aligned. The reason this release is still misaligned is because #1294 was targeted at 24.02 rather than 23.12.

@jakirkham
Copy link
Member Author

Am able to pip install dask-cuda now that rapids-dask-dependency

Closing as resolved

That said, we should keep an eye out for similar issues in 24.02 as the release process is ironed out (still a few moving parts as noted above)

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

No branches or pull requests

2 participants