[Python-checkins] python/dist/src/Doc/api init.tex,1.23,1.24

[mwh@users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Doc/api
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7251

Modified Files:
	init.tex 
Log Message:
fix some silly whitespace stuff (must have hit M-q or something?)


Index: init.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/api/init.tex,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- init.tex	13 Feb 2005 22:50:02 -0000	1.23
+++ init.tex	20 Jun 2005 12:12:45 -0000	1.24
@@ -471,10 +471,10 @@
     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 @@
 \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