-
Is this a duplicate?
Areacuda.bindings Is your feature request related to a problem? Please describe.I would like some method to ensure that all CUDA libraries have matching major and minor versions in order to ensure compatibility. For example, if I (on Linux) Describe the solution you'd likeI would like major and minor versions of CUDA packages to be able to be constrained together. This might look like Describe alternatives you've consideredI've tried a few different packages that I hoped to apply this constraint somehow. None seemed to. Part of the complication here is that PyTorch manages CUDA versions with an index flag that can't be embedded in Additional contextThis could possibly be a |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @jmulcahy sorry for late reply. @emmatyping-nv has been working on meeting this exact needs for some time, and I am happy to share that the new |
Beta Was this translation helpful? Give feedback.
Hi @jmulcahy sorry for late reply. @emmatyping-nv has been working on meeting this exact needs for some time, and I am happy to share that the new
cuda-toolkit
metapackage is released on PyPI. It supports CUDA 11.8, 12.x, and 13.x. For example, you can build a consistent 12.9 environment by doingpip install cuda-toolkit[nvcc,nvrtc]=12.9
. Please let us know if you encounter any issue. CUDA Python projects will start to use this new machinery going forward (#853).