-
Notifications
You must be signed in to change notification settings - Fork 107
remove RAPIDS dependencies from cu12, cu13 extras #1549
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
105ed4b
remove RAPIDS dependencies from cu12, cu13 extras
jameslamb 0b0acd6
ugh, a 25.8 snuck in there
jameslamb ae52b0a
remove ucx-py
jameslamb bfe3317
add numba-cuda back to runtime deps
jameslamb fc467d3
add cuda-core runtime dependency
jameslamb c49210e
wildcard specs are spelled differently for conda
jameslamb File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still want
numba-cudato be installed for testing only, this ensuresdask-cuda/dask_cuda/tests/test_gds.py
Lines 30 to 32 in 224a407
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#1531 added
numba-cudaas a runtime dependency, don't the reasons for that PR still hold, and therefore shouldn'tnumba-cudacontinue to be a runtime dependency?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes, that's right, the conda environment files got me confused, why is
numba-cudaremoved from there, shouldn't it be in there too to satisfy it?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahhhh yes YOU are right!
When I saw those removals I thought "ok, makes sense, runtime dependencies get installed via the package metadata for
dask-cuda, not pre-installed in the environment" but I don't think that's what we usually do in RAPIDS for those conda env files checked into the repo.All the other runtime dependencies (like
pandas) are in there.I just pushed bfe3317 restoring it as a runtime dependency. Now
numba-cudawill be in those conda env files, and it'll also show up in the wheel's strong runtime dependencies.I think this should be ok, and is actually desirable.
Having one dependency with constraints and one without should be fine. Tested like this:
And saw it succeed and respect
numba-cuda's constraints, like this:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, but wait, we did make a decision to NOT depend on numba-cuda anymore in favor of
cuda-bindings, no? I think I'm confused to why we need it to be a runtime in dask-cuda, presumably because ofcudf-cu[12,13]? This is what I previously proposed, and I thought that's what we ultimately had done/intended to do in #1536 . Am I mixing things up again?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From that link I shared, it looks to me like
cuda-coredepends (optionally, via a[cu12,13]extra) oncuda-bindings, not the other way around.https://github.com/NVIDIA/cuda-python/blob/fa07cf58ef5c70bb6a42e9aa859487e88f5699a2/cuda_core/pyproject.toml#L50-L51
Depending on
cuda-bindingsalone won't bring incuda-core.docker run \ --rm \ --gpus all \ -it rapidsai/citestwheel:25.10-cuda12.9.1-ubuntu24.04-py3.13 \ bash # install 'cuda-bindings' (no version) pip install cuda-bindingsInstalling
cuda-bindingswithout a version pulls in CUDA 13 versions ofcuda-bindingsandcuda-pathfinder:And the
cuda.corenamespace is not available.So I think we want the following for
dask-cuda's runtime requirementsdask-cuda -> cuda-core>=12.0,<14dask-cuda[cu12] -> cuda-core[cu12]==12.*dask-cuda[cu13] -> cuda-core[cu13]==13.*There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's what I wanted to say,
cuda-bindingswould allow a proper existing environment to work. It's looking more and more like there's no way around it, let's just pincuda-coreas you proposed, it seems that is the only correct pin, unfortunately. Could you do that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok yep, I can do that!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah one clarification...
cuda-core's versioning does not follow the CTK, sorry for that mistake.So it'd be:
dask-cuda -> cuda-core==0.3.*dask-cuda[cu12] -> cuda-core[cu12]==0.3.*dask-cuda[cu13] -> cuda-core[cu13]==0.3.*Matching this pin that's already there in
dask-cuda's test environment:dask-cuda/dependencies.yaml
Line 162 in c749356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added that in fc467d3