mirror of
https://github.com/python/cpython.git
synced 2025-08-04 08:59:19 +00:00
bpo-38600: NULL -> `NULL
`. (GH-17001)
Also fix some other formatting.
This commit is contained in:
parent
1d8da61f5a
commit
e835b31d2b
27 changed files with 68 additions and 68 deletions
|
@ -19,9 +19,9 @@ return ``1`` for success and ``0`` for failure).
|
|||
|
||||
Concretely, the error indicator consists of three object pointers: the
|
||||
exception's type, the exception's value, and the traceback object. Any
|
||||
of those pointers can be NULL if non-set (although some combinations are
|
||||
forbidden, for example you can't have a non-NULL traceback if the exception
|
||||
type is NULL).
|
||||
of those pointers can be ``NULL`` if non-set (although some combinations are
|
||||
forbidden, for example you can't have a non-``NULL`` traceback if the exception
|
||||
type is ``NULL``).
|
||||
|
||||
When a function must fail because some function it called failed, it generally
|
||||
doesn't set the error indicator; the function it called already set it. It is
|
||||
|
@ -92,7 +92,7 @@ Raising exceptions
|
|||
|
||||
These functions help you set the current thread's error indicator.
|
||||
For convenience, some of these functions will always return a
|
||||
NULL pointer for use in a ``return`` statement.
|
||||
``NULL`` pointer for use in a ``return`` statement.
|
||||
|
||||
|
||||
.. c:function:: void PyErr_SetString(PyObject *type, const char *message)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue