Currently RAPIDS depends on cuda-python. However cuda-python is being turned into a metapackage (NVIDIA/cuda-python#105) that pulls in much more than what RAPIDS strictly needs.
To more narrowly define what RAPIDS needs and uses, it would be better to move to cuda-bindings and if necessary cuda-core.
Approach
Update conda recipes, dependencies.yaml, etc. for RAPIDS projects to use only the individual libraries within cuda-python that RAPIDS needs.
You can roughly tell which need cuda-bindings and/or cuda-core like this:
git grep -E 'from cuda.*import|import cuda'
('NVIDIA' search | 'rapidsai' search)
Repo updates
Follow-ups
Currently RAPIDS depends on
cuda-python. Howevercuda-pythonis being turned into a metapackage (NVIDIA/cuda-python#105) that pulls in much more than what RAPIDS strictly needs.To more narrowly define what RAPIDS needs and uses, it would be better to move to
cuda-bindingsand if necessarycuda-core.Approach
Update conda recipes,
dependencies.yaml, etc. for RAPIDS projects to use only the individual libraries withincuda-pythonthat RAPIDS needs.You can roughly tell which need
cuda-bindingsand/orcuda-corelike this:git grep -E 'from cuda.*import|import cuda'('NVIDIA' search | 'rapidsai' search)
Repo updates
Follow-ups