Zengtudor
/
pybind11
mirror of https://github.com/pybind/pybind11.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix code formatting

This commit is contained in:
jiwaszki 2024-09-05 23:59:11 +02:00
parent 7266988540
commit 2fbd013434
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/advanced/exceptions.rst
View File

@ -333,9 +333,9 @@ Handling warnings from the Python C API
Where possible, use :ref:`pybind11 warnings <warnings>` instead of calling Where possible, use :ref:`pybind11 warnings <warnings>` instead of calling
the Python C API directly. The motivation is similar to previously mentioned errors. the Python C API directly. The motivation is similar to previously mentioned errors.
All warnings categories are required to be a subclass of `PyExc_Warning` from Python C API. All warnings categories are required to be a subclass of ``PyExc_Warning`` from Python C API.
Warnings can be raised with `warn` function: Warnings can be raised with ``warn`` function:
.. code-block:: cpp .. code-block:: cpp
@ -344,7 +344,7 @@ Warnings can be raised with `warn` function:
// When calling `stack_level` can be specified as well. // When calling `stack_level` can be specified as well.
py::warnings::warn("Another one!", PyExc_DeprecationWarning, 3); py::warnings::warn("Another one!", PyExc_DeprecationWarning, 3);
New warning types can be registered on the module level with `new_warning_type`: New warning types can be registered on the module level with ``new_warning_type``:
.. code-block:: cpp .. code-block:: cpp