Update CUDA requirements in 25.08 installation guide #662
Conversation
✅ Deploy Preview for docs-rapids-ai ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
| <div class="options-section" x-show="active_method !== 'pip'"> | ||
| <div class="option-label">Python</div> | ||
| <template x-for="version in python_vers"> | ||
| <template x-for="version in getSupportedPythonVersions()"> |
There was a problem hiding this comment.
Thank you for this! Fewer paths for configuration = fewer surprises 😁
jameslamb
left a comment
jameslamb
left a comment
There was a problem hiding this comment.
I clicked around the install selector in the preview and this all looks great. I don't know it technically counts as the scope of this, but I have 2 more small suggestions.
Approving because I'm also good with what this looks like right now, do what you want with this.
Suggestion 1: specify a minimum pip
If I was reading this line, I might think "how do I know if the pip I have has support for PEP-600?":
Line 113 in 0786221
The first pip to support PEP-600 was 20.3: pypa/pip#9077
We could make it easier for people... we should recommend pip install -U 'pip>=20.3'.
Suggestion 2: simplify pip index requirement
I don't think this language about "the initial experimental release" is very helpful:
Line 111 in 0786221
That statement "The pip index has moved from the initial experimental release!" could safely be removed.
2 participants
In 25.08, there were a few significant changes in CUDA support.
This PR updates those and also thoroughly revises the installation notes and troubleshooting info. In many places, we had outdated information that is no longer relevant with CUDA 12+.
I also removed notes pertaining to CUDA 11, updated a lot of links, fixed installation instructions for
nvidia-container-toolkit, and removed workarounds for non-RAPIDS software older than 2023.