From e30ac5703850d50a36bcf09ee1fe61b9764e4ab9 Mon Sep 17 00:00:00 2001 From: Thomas Wouters Date: Mon, 9 Jul 2001 14:35:01 +0000 Subject: [PATCH] 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'. --- Doc/api/api.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/api/api.tex b/Doc/api/api.tex index 4c55b9691bb..44a3d35ee05 100644 --- a/Doc/api/api.tex +++ b/Doc/api/api.tex @@ -4598,14 +4598,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