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

(cherry picked from commit 9ed0aee2)

bpo-32687: Fix wrong meaning of args for PyTrace_LINE/CALL in documentation (GH-5361) (GH-5378)
(cherry picked from commit 9ed0aee2)
745e9de7 · Miss Islington (bot) · Xiang Zhang · 38487a05 · 745e9de7
Commit 745e9de7 authored Jan 28, 2018 by Miss Islington (bot) Committed by Xiang Zhang 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
@@ -983,12 +983,12 @@ 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. |