Use exception:: directive to document exceptions instead of data::

Author: antonwolfy

doc/reference/exceptions.rst

@@ -1,67 +1,71 @@
 .. _routines.exceptions:
 
+.. py:module:: dpnp.exceptions
+
 Exceptions and Warnings
 =======================
 
 General exceptions used by DPNP. Note that some exceptions may be module
 specific, such as linear algebra errors.
 
-.. currentmodule:: dpnp.exceptions
-
 Exceptions
 ----------
 
-.. data:: AxisError
+.. exception:: AxisError
+
+   Given when an axis is invalid.
+
+.. exception:: DLPackCreationError
 
-    Given when an axis is invalid.
+   Given when constructing DLPack capsule from either :class:`dpnp.ndarray` or
+   :class:`dpctl.tensor.usm_ndarray` based on a USM allocation
+   on a partitioned SYCL device.
 
-.. data:: DLPackCreationError
+   .. rubric:: Examples
 
-    Given when constructing DLPack capsule from either :class:`dpnp.ndarray` or
-    :class:`dpctl.tensor.usm_ndarray` based on a USM allocation
-    on a partitioned SYCL device.
+   .. code-block:: python
 
-    .. rubric:: Examples
+      >>> import dpnp as np
+      >>> import dpctl
+      >>> dev = dpctl.SyclDevice('cpu')
+      >>> sdevs = dev.create_sub_devices(partition=[1, 1])
+      >>> q = dpctl.SyclQueue(sdevs[0])
+      >>> x = np.ones(10, sycl_queue=q)
+      >>> np.from_dlpack(x)
+      Traceback (most recent call last):
+      ...
+      DLPackCreationError: to_dlpack_capsule: DLPack can only export arrays based on USM allocations bound to a default platform SYCL context
 
-    .. code-block:: python
+.. exception:: ExecutionPlacementError
 
-        >>> import dpnp as np
-        >>> import dpctl
-        >>> dev = dpctl.SyclDevice('cpu')
-        >>> sdevs = dev.create_sub_devices(partition=[1, 1])
-        >>> q = dpctl.SyclQueue(sdevs[0])
-        >>> x = np.ones(10, sycl_queue=q)
-        >>> np.from_dlpack(x)
-        Traceback (most recent call last):
-        ...
-        DLPackCreationError: to_dlpack_capsule: DLPack can only export arrays based on USM allocations bound to a default platform SYCL context
+   Given when execution placement target can not be unambiguously determined
+   from input arrays. Make sure that input arrays are associated with the same
+   :class:`dpctl.SyclQueue`, or migrate data to the same
+   :class:`dpctl.SyclQueue` using :meth:`dpnp.ndarray.to_device` method.
 
-.. data:: ExecutionPlacementError
+.. exception:: SyclContextCreationError
 
-    Given when execution placement target can not be unambiguously determined
-    from input arrays. Make sure that input arrays are associated with the same
-    :class:`dpctl.SyclQueue`, or migrate data to the same
-    :class:`dpctl.SyclQueue` using :meth:`dpnp.ndarray.to_device` method.
+   Given when :class:`dpctl.SyclContext` instance could not be created.
 
-.. data:: SyclContextCreationError
+.. exception:: SyclDeviceCreationError
 
-    Given when :class:`dpctl.SyclContext` instance could not be created.
+   Given when :class:`dpctl.SyclDevice` instance could not be created.
 
-.. data:: SyclDeviceCreationError
+.. exception:: SyclQueueCreationError
 
-    Given when :class:`dpctl.SyclDevice` instance could not be created.
+   Given when :class:`dpctl.SyclQueue` instance could not be created.
+   The creation can fail if the filter string is invalid, or the backend or
+   device type values are not supported.
 
-.. data:: SyclQueueCreationError
+.. exception:: USMAllocationError
 
-    Given when :class:`dpctl.SyclQueue` instance could not be created.
-    The creation can fail if the filter string is invalid, or the backend or
-    device type values are not supported.
+   Given when Unified Shared Memory (USM) allocation call returns a null
+   pointer, signaling a failure to perform the allocation.
+   Some common reasons for allocation failure are:
 
-.. data:: USMAllocationError
+      * insufficient free memory to perform the allocation request
+      * allocation size exceeds the maximum supported by targeted backend
 
-    Given when Unified Shared Memory (USM) allocation call returns a null
-    pointer, signaling a failure to perform the allocation.
-    Some common reasons for allocation failure are:
 
-        * insufficient free memory to perform the allocation request
-        * allocation size exceeds the maximum supported by targeted backend
+.. automodule:: dpnp.exceptions
+    :no-index: