mirror of
https://github.com/python/cpython.git
synced 2025-08-04 00:48:58 +00:00
gh-93738: Documentation C syntax (Function glob patterns -> literal markup) (#97774)
This commit is contained in:
parent
09aea94d29
commit
0e72606dd4
7 changed files with 20 additions and 20 deletions
|
@ -14,7 +14,7 @@ there is a global indicator (per thread) of the last error that occurred. Most
|
|||
C API functions don't clear this on success, but will set it to indicate the
|
||||
cause of the error on failure. Most C API functions also return an error
|
||||
indicator, usually ``NULL`` if they are supposed to return a pointer, or ``-1``
|
||||
if they return an integer (exception: the :c:func:`PyArg_\*` functions
|
||||
if they return an integer (exception: the ``PyArg_*`` functions
|
||||
return ``1`` for success and ``0`` for failure).
|
||||
|
||||
Concretely, the error indicator consists of three object pointers: the
|
||||
|
@ -370,7 +370,7 @@ Querying the error indicator
|
|||
.. c:function:: PyObject* PyErr_Occurred()
|
||||
|
||||
Test whether the error indicator is set. If set, return the exception *type*
|
||||
(the first argument to the last call to one of the :c:func:`PyErr_Set\*`
|
||||
(the first argument to the last call to one of the ``PyErr_Set*``
|
||||
functions or to :c:func:`PyErr_Restore`). If not set, return ``NULL``. You do not
|
||||
own a reference to the return value, so you do not need to :c:func:`Py_DECREF`
|
||||
it.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue