Skip to content

Commit 449ca6d

Browse files
committed
Debug rendering of dpnp.exceptions.DLPackCreationError
1 parent dd052fc commit 449ca6d

File tree

1 file changed

+34
-25
lines changed

1 file changed

+34
-25
lines changed

doc/reference/exceptions.rst

Lines changed: 34 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -6,16 +6,25 @@ Exceptions and Warnings
66
General exceptions used by DPNP. Note that some exceptions may be module
77
specific, such as linear algebra errors.
88

9-
.. currentmodule:: dpnp.exceptions
9+
.. .. currentmodule:: dpnp.exceptions
1010
1111
Exceptions
1212
----------
1313

14-
.. data:: AxisError
14+
.. automodule:: dpnp.exceptions
15+
:members:
16+
:undoc-members:
17+
:show-inheritance:
18+
19+
.. .. data:: AxisError
1520
16-
Given when an axis is invalid.
21+
.. Given when an axis is invalid.
1722
18-
.. data:: DLPackCreationError
23+
.. .. data:: DLPackCreationError
24+
25+
.. autoclass:: dpnp.exceptions.DLPackCreationError
26+
:show-inheritance:
27+
:noindex:
1928

2029
Given when constructing DLPack capsule from either :class:`dpnp.ndarray` or
2130
:class:`dpctl.tensor.usm_ndarray` based on a USM allocation
@@ -36,35 +45,35 @@ Exceptions
3645
...
3746
DLPackCreationError: to_dlpack_capsule: DLPack can only export arrays based on USM allocations bound to a default platform SYCL context
3847
39-
.. data:: ExecutionPlacementError
48+
.. .. data:: ExecutionPlacementError
4049
41-
Given when execution placement target can not be unambiguously determined
42-
from input arrays. Make sure that input arrays are associated with the same
43-
:class:`dpctl.SyclQueue`, or migrate data to the same
44-
:class:`dpctl.SyclQueue` using :meth:`dpnp.ndarray.to_device` method.
50+
.. Given when execution placement target can not be unambiguously determined
51+
.. from input arrays. Make sure that input arrays are associated with the same
52+
.. :class:`dpctl.SyclQueue`, or migrate data to the same
53+
.. :class:`dpctl.SyclQueue` using :meth:`dpnp.ndarray.to_device` method.
4554
46-
.. data:: SyclContextCreationError
55+
.. .. data:: SyclContextCreationError
4756
48-
Given when :class:`dpctl.SyclContext` instance could not be created.
57+
.. Given when :class:`dpctl.SyclContext` instance could not be created.
4958
50-
.. data:: SyclDeviceCreationError
59+
.. .. data:: SyclDeviceCreationError
5160
52-
Given when :class:`dpctl.SyclDevice` instance could not be created.
61+
.. Given when :class:`dpctl.SyclDevice` instance could not be created.
5362
54-
.. data:: SyclQueueCreationError
63+
.. .. data:: SyclQueueCreationError
5564
56-
Given when :class:`dpctl.SyclQueue` instance could not be created.
57-
The creation can fail if the filter string is invalid, or the backend or
58-
device type values are not supported.
65+
.. Given when :class:`dpctl.SyclQueue` instance could not be created.
66+
.. The creation can fail if the filter string is invalid, or the backend or
67+
.. device type values are not supported.
5968
60-
.. data:: USMAllocationError
69+
.. .. data:: USMAllocationError
6170
62-
Given when Unified Shared Memory (USM) allocation call returns a null
63-
pointer, signaling a failure to perform the allocation.
64-
Some common reasons for allocation failure are:
71+
.. Given when Unified Shared Memory (USM) allocation call returns a null
72+
.. pointer, signaling a failure to perform the allocation.
73+
.. Some common reasons for allocation failure are:
6574
66-
* insufficient free memory to perform the allocation request
67-
* allocation size exceeds the maximum supported by targeted backend
75+
.. * insufficient free memory to perform the allocation request
76+
.. * allocation size exceeds the maximum supported by targeted backend
6877
69-
.. automodule:: dpnp.exceptions
70-
:no-index:
78+
.. .. automodule:: dpnp.exceptions
79+
.. :no-index:

0 commit comments

Comments
 (0)