bpo-37363: Document internal audit events (GH-14663)

Three internal cpython events were not documented, yet.

Signed-off-by: Christian Heimes <christian@python.org>



https://bugs.python.org/issue37363
This commit is contained in:
Christian Heimes 2019-09-12 15:13:02 +02:00 committed by Miss Islington (bot)
parent f9dc2ad890
commit ed4b3216e5
1 changed files with 6 additions and 1 deletions

View File

@ -301,8 +301,9 @@ Initializing and finalizing the interpreter
than once; this can happen if an application calls :c:func:`Py_Initialize` and
:c:func:`Py_FinalizeEx` more than once.
.. versionadded:: 3.6
.. audit-event:: cpython._PySys_ClearAuditHooks "" c.Py_FinalizeEx
.. versionadded:: 3.6
.. c:function:: void Py_Finalize()
@ -992,12 +993,16 @@ All of the following functions must be called after :c:func:`Py_Initialize`.
be held, but may be held if it is necessary to serialize calls to this
function.
.. audit-event:: cpython.PyInterpreterState_New "" c.PyInterpreterState_New
.. c:function:: void PyInterpreterState_Clear(PyInterpreterState *interp)
Reset all information in an interpreter state object. The global interpreter
lock must be held.
.. audit-event:: cpython.PyInterpreterState_Clear "" c.PyInterpreterState_Clear
.. c:function:: void PyInterpreterState_Delete(PyInterpreterState *interp)