summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael W. Hudson <mwh@python.net>2005-06-20 12:12:45 (GMT)
committerMichael W. Hudson <mwh@python.net>2005-06-20 12:12:45 (GMT)
commit7b279078c0f59c37a91062ebf724f8f13287d5d6 (patch)
tree7170b86243570e90f8ccc3a734f96dbf8ca25fe4
parente5a0a9609faea9afdc6f81f1f6dfa07b1437e3ae (diff)
downloadcpython-7b279078c0f59c37a91062ebf724f8f13287d5d6.zip
cpython-7b279078c0f59c37a91062ebf724f8f13287d5d6.tar.gz
cpython-7b279078c0f59c37a91062ebf724f8f13287d5d6.tar.bz2
fix some silly whitespace stuff (must have hit M-q or something?)
-rw-r--r--Doc/api/init.tex26
1 files changed, 13 insertions, 13 deletions
diff --git a/Doc/api/init.tex b/Doc/api/init.tex
index 96a13d3..940aab9 100644
--- a/Doc/api/init.tex
+++ b/Doc/api/init.tex
@@ -471,10 +471,10 @@ thread is now:
PyGILState_Release(gstate);
\end{verbatim}
-Note that the \cfunction{PyGILState_*()} functions assume there is only
-one global interpreter (created automatically by
+Note that the \cfunction{PyGILState_*()} functions assume there is
+only one global interpreter (created automatically by
\cfunction{Py_Initialize()}). Python still supports the creation of
-additional interpreters (using \cfunction{Py_NewInterpreter()}), but
+additional interpreters (using \cfunction{Py_NewInterpreter()}), but
mixing multiple interpreters and the \cfunction{PyGILState_*()} API is
unsupported.
@@ -697,16 +697,16 @@ interpreter lock has been created.
\end{cfuncdesc}
\begin{cfuncdesc}{PyGILState_STATE}{PyGILState_Ensure}{}
-Ensure that the current thread is ready to call the Python
-C API regardless of the current state of Python, or of its
-thread lock. This may be called as many times as desired
-by a thread as long as each call is matched with a call to
-\cfunction{PyGILState_Release()}.
-In general, other thread-related APIs may
-be used between \cfunction{PyGILState_Ensure()} and \cfunction{PyGILState_Release()} calls as long as the
-thread state is restored to its previous state before the Release().
-For example, normal usage of the \csimplemacro{Py_BEGIN_ALLOW_THREADS}
-and \csimplemacro{Py_END_ALLOW_THREADS} macros is acceptable.
+Ensure that the current thread is ready to call the Python C API
+regardless of the current state of Python, or of its thread lock.
+This may be called as many times as desired by a thread as long as
+each call is matched with a call to \cfunction{PyGILState_Release()}.
+In general, other thread-related APIs may be used between
+\cfunction{PyGILState_Ensure()} and \cfunction{PyGILState_Release()}
+calls as long as the thread state is restored to its previous state
+before the Release(). For example, normal usage of the
+\csimplemacro{Py_BEGIN_ALLOW_THREADS} and
+\csimplemacro{Py_END_ALLOW_THREADS} macros is acceptable.
The return value is an opaque "handle" to the thread state when
\cfunction{PyGILState_Acquire()} was called, and must be passed to