Fix for SF bug #436525, reported by Greg Kochanski:

The block/unblock thread macros are called 'Py_BLOCK_THREADS' and
'Py_UNBLOCK_THREADS', not 'Py_BEGIN_BLOCK_THREADS' and
'Py_BEGIN_UNBLOCK_THREADS'.

diff --git a/Doc/api/api.tex b/Doc/api/api.tex
index 5cc3dfdfa05a2e8d50836d7ae346c8a14686b4d5..fab6ae0e2bd20212a53880678925e172c9940aaf 100644 (file)
--- a/Doc/api/api.tex
+++ b/Doc/api/api.tex
@@ -4539,14 +4539,14 @@ discussion of this macro.  It is a no-op when thread support is
 disabled at compile time.
 \end{csimplemacrodesc}
 
-\begin{csimplemacrodesc}{Py_BEGIN_BLOCK_THREADS}
+\begin{csimplemacrodesc}{Py_BLOCK_THREADS}
 This macro expands to \samp{PyEval_RestoreThread(_save);} i.e. it
 is equivalent to \code{Py_END_ALLOW_THREADS} without the closing
 brace.  It is a no-op when thread support is disabled at compile
 time.
 \end{csimplemacrodesc}
 
-\begin{csimplemacrodesc}{Py_BEGIN_UNBLOCK_THREADS}
+\begin{csimplemacrodesc}{Py_UNBLOCK_THREADS}
 This macro expands to \samp{_save = PyEval_SaveThread();} i.e. it is
 equivalent to \code{Py_BEGIN_ALLOW_THREADS} without the opening brace
 and variable declaration.  It is a no-op when thread support is