Skip to content

Commit 818a62f

Browse files
Andy-Jostclaude
andcommitted
docs(cuda.core): advise against pinning cuda-bindings next to cuda-core
Users who pin cuda-bindings themselves can conflict with the floor of a later cuda-core release. Tell them to depend on cuda-core with the cu12 or cu13 extra and let cuda-core choose the cuda-bindings version. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 97d77db commit 818a62f

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

‎cuda_core/docs/source/install.rst‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,10 @@ If you upgrade ``cuda-core`` alone, the installed ``cuda-bindings`` can be older
5959
release requires. ``import cuda.core`` then reports the required version and the ``pip`` command
6060
that installs it.
6161

62+
Do not pin ``cuda-bindings`` in your own requirements. Depend on ``cuda-core`` with the ``cu12``
63+
or ``cu13`` extra, and let ``cuda-core`` choose the ``cuda-bindings`` version. A pin of your own
64+
can conflict with the floor of a later ``cuda-core`` release.
65+
6266

6367
Installing from Conda (conda-forge)
6468
-----------------------------------
@@ -73,6 +77,7 @@ and likewise use ``cuda-version=13`` for CUDA 13.
7377

7478
The conda-forge package depends on ``cuda-bindings`` of the same CUDA major. The
7579
``cuda-bindings`` floor of the release also applies to it. See :ref:`cuda-core-bindings-floor`.
80+
As with ``pip``, do not pin ``cuda-bindings`` yourself. Let ``cuda-core`` choose it.
7681

7782

7883
Development environment

0 commit comments

Comments
 (0)