switch from 'cuda-python' to specific components (e.g. 'cuda-bindings')#3068
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
📝 WalkthroughWalkthroughThis PR replaces the Changescuda-python to cuda-bindings migration
Estimated code review effort: 2 (Simple) | ~10 minutes Related PRs: None identified. Suggested labels: dependencies, conda Suggested reviewers: None identified. 🐰 A rabbit hops through YAML fields anew, 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/merge |
Description
Contributes to rapidsai/build-planning#285
cuda-pythonis a metapackage and sometimes pulls in components that RAPIDS libraries don't need. This PR is part of a series dropping direct use ofcuda-pythonin favor of depending only on those specific components.cuda-pythoncuda-bindings >=12.9.2,<13.0(CUDA 12),cuda-bindings >=13.0.1,<14.0(CUDA 13)cuda-bindingsin CINotes for Reviewers
Why these specific bounds?
cuda-pythoncuda-bindingsmajor version follows the CTK major version, so kept a ceiling just like we currently have forcuda-python