bpo-32687: Fix wrong meaning of args for PyTrace_LINE/CALL in documentation (#5361)

9ed0aee2 · Xiang Zhang · GitHub · a278ad2f · 9ed0aee2
Commit 9ed0aee2 authored Jan 28, 2018 by Xiang Zhang Committed by GitHub Jan 28, 2018
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 2 deletions

Doc/c-api/init.rst Doc/c-api/init.rst +2 -2

No files found.
--- 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. |