summaryrefslogtreecommitdiff
path: root/Doc/c-api/exceptions.rst
diff options
context:
space:
mode:
authorJeroen Demeyer <jeroen.k.demeyer@gmail.com>2019-11-12 14:08:00 +0100
committerMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2019-11-12 05:08:00 -0800
commit9a13a388f202268dd7b771638adbec132449b98b (patch)
tree71496af5abeb5a5737a5f490d8b53dbb91e6ed02 /Doc/c-api/exceptions.rst
parenta12255d8def0c82560545e66c1be981a447751c3 (diff)
downloadcpython-git-9a13a388f202268dd7b771638adbec132449b98b.tar.gz
bpo-36974: expand call protocol documentation (GH-13844)
CC @encukou I'm also adding Petr Viktorin as contributor for vectorcall in the "what's new" section. https://bugs.python.org/issue36974 Automerge-Triggered-By: @encukou Automerge-Triggered-By: @encukou
Diffstat (limited to 'Doc/c-api/exceptions.rst')
-rw-r--r--Doc/c-api/exceptions.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst
index cd6df00aeb..2edcbf788d 100644
--- a/Doc/c-api/exceptions.rst
+++ b/Doc/c-api/exceptions.rst
@@ -697,6 +697,8 @@ The following functions are used to create and modify Unicode exceptions from C.
``0`` on success, ``-1`` on failure.
+.. _recursion:
+
Recursion Control
=================
@@ -704,6 +706,8 @@ These two functions provide a way to perform safe recursive calls at the C
level, both in the core and in extension modules. They are needed if the
recursive code does not necessarily invoke Python code (which tracks its
recursion depth automatically).
+They are also not needed for *tp_call* implementations
+because the :ref:`call protocol <call>` takes care of recursion handling.
.. c:function:: int Py_EnterRecursiveCall(const char *where)