traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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'.
This commit is contained in:
Thomas Wouters 2001-07-09 14:35:01 +00:00
parent efafcea280
commit e30ac57038
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/api/api.tex
View File

@ -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