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

(cherry picked from commit 9ed0aee27c)
This commit is contained in:
Miss Islington (bot) 2018-01-28 00:41:05 -08:00 committed by Xiang Zhang
parent 0135dfdc1f
commit 854f0424de

View file

@ -1063,12 +1063,12 @@ Python-level trace functions in previous versions.
+------------------------------+--------------------------------------+ +------------------------------+--------------------------------------+
| Value of *what* | Meaning of *arg* | | 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 | | :const:`PyTrace_EXCEPTION` | Exception information as returned by |
| | :func:`sys.exc_info`. | | | :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, | | :const:`PyTrace_RETURN` | Value being returned to the caller, |
| | or *NULL* if caused by an exception. | | | or *NULL* if caused by an exception. |