Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
docs(cuda.core): name the exception classes importable from cuda.core
  • Loading branch information
srimanachanta committed Oct 31, 2026
commit 49f28b651998d914f0ecede9273913861c081147
8 changes: 4 additions & 4 deletions cuda_core/docs/source/error_handling.rst
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,10 @@ exception whose message contains the error name and its description:
:class:`NVRTCError` for NVRTC failures, and the ``cuda.bindings`` error types
for NVVM and nvJitLink failures. A driver or runtime call that runs out of
memory raises :class:`CUDAOutOfMemoryError`, which derives from both
:class:`CUDAError` and :class:`MemoryError`. These exception classes are
importable from the top-level ``cuda.core`` namespace. Invalid arguments and
misuse raise the usual Python exception types (``TypeError``, ``ValueError``,
``RuntimeError``).
:class:`CUDAError` and :class:`MemoryError`. :class:`CUDAError`,
:class:`NVRTCError`, and :class:`CUDAOutOfMemoryError` are importable from the
top-level ``cuda.core`` namespace. Invalid arguments and misuse raise the
usual Python exception types (``TypeError``, ``ValueError``, ``RuntimeError``).

When a ``cuda.core`` call raises, the following hold:

Expand Down
Loading