From: Xiang Zhang Date: Sun, 28 Jan 2018 07:38:21 +0000 (+0800) Subject: bpo-32687: Fix wrong meaning of args for PyTrace_LINE/CALL in documentation (#5361) X-Git-Tag: v3.7.0b1~64 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9ed0aee27c249dada410a22fff4325a4a61df36d;p=python bpo-32687: Fix wrong meaning of args for PyTrace_LINE/CALL in documentation (#5361) --- diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst index 86faf47f53..9887d28b09 100644 --- a/Doc/c-api/init.rst +++ b/Doc/c-api/init.rst @@ -1283,12 +1283,12 @@ Python-level trace functions in previous versions. +------------------------------+--------------------------------------+ | Value of *what* | Meaning of *arg* | +==============================+======================================+ - | :const:`PyTrace_CALL` | Always *NULL*. | + | :const:`PyTrace_CALL` | Always :c:data:`Py_None`. | +------------------------------+--------------------------------------+ | :const:`PyTrace_EXCEPTION` | Exception information as returned by | | | :func:`sys.exc_info`. | +------------------------------+--------------------------------------+ - | :const:`PyTrace_LINE` | Always *NULL*. | + | :const:`PyTrace_LINE` | Always :c:data:`Py_None`. | +------------------------------+--------------------------------------+ | :const:`PyTrace_RETURN` | Value being returned to the caller, | | | or *NULL* if caused by an exception. |