From: Thomas Wouters <thomas@python.org>
Date: Mon, 9 Jul 2001 14:34:16 +0000 (+0000)
Subject: Fix for SF bug #436525, reported by Greg Kochanski:
X-Git-Tag: v2.1.1c1~22
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=42af3cedd9e072d6a6d2dd0cb17b38d00e19f397;p=thirdparty%2FPython%2Fcpython.git

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 5cc3dfdfa05a..fab6ae0e2bd2 100644
--- 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