Skip to content

Commit 9ed0aee

Browse files
authored
bpo-32687: Fix wrong meaning of args for PyTrace_LINE/CALL in documentation (#5361)
1 parent a278ad2 commit 9ed0aee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Doc/c-api/init.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1283,12 +1283,12 @@ Python-level trace functions in previous versions.
12831283
+------------------------------+--------------------------------------+
12841284
| Value of *what* | Meaning of *arg* |
12851285
+==============================+======================================+
1286-
| :const:`PyTrace_CALL` | Always *NULL*. |
1286+
| :const:`PyTrace_CALL` | Always :c:data:`Py_None`. |
12871287
+------------------------------+--------------------------------------+
12881288
| :const:`PyTrace_EXCEPTION` | Exception information as returned by |
12891289
| | :func:`sys.exc_info`. |
12901290
+------------------------------+--------------------------------------+
1291-
| :const:`PyTrace_LINE` | Always *NULL*. |
1291+
| :const:`PyTrace_LINE` | Always :c:data:`Py_None`. |
12921292
+------------------------------+--------------------------------------+
12931293
| :const:`PyTrace_RETURN` | Value being returned to the caller, |
12941294
| | or *NULL* if caused by an exception. |

0 commit comments

Comments
 (0)