summaryrefslogtreecommitdiffstats
path: root/doc/libpythonize.html
diff options
context:
space:
mode:
authorDarrell Anderson <humanreadable@yahoo.com>2013-05-04 23:53:07 -0500
committerDarrell Anderson <humanreadable@yahoo.com>2013-05-04 23:53:07 -0500
commit1a59ddcb5a76647bd1a3f19fd055649f70282f0e (patch)
treeff89038a3ccd7c5d7adfbcc69ea8ff22e6019831 /doc/libpythonize.html
parent8b135bd3e5b2f552157b9e19afa7e600c6898856 (diff)
downloadpytde-1a59ddcb5a76647bd1a3f19fd055649f70282f0e.tar.gz
pytde-1a59ddcb5a76647bd1a3f19fd055649f70282f0e.zip
Fix inadvertent renaming.
Diffstat (limited to 'doc/libpythonize.html')
-rw-r--r--doc/libpythonize.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/libpythonize.html b/doc/libpythonize.html
index 0aae9a2..f49fc63 100644
--- a/doc/libpythonize.html
+++ b/doc/libpythonize.html
@@ -50,7 +50,7 @@ the lock is not released, access will be denied to Python code relying on the in
bindings like PyTQt or PyKDE).
</p>
<p>
-If a second instance of Pythonize is created (within the same parent process), that instance will actquire
+If a second instance of Pythonize is created (within the same parent process), that instance will acquire
the lock automatically. In order to allow a second (and third or more) instance of Pythonize to be
created and obtain the lock, it's necessary to have a related thread state (PyThreadState). This thread
state is created by a call to PyThreadState_Get when the first instance of Pythonize is created. The
@@ -87,11 +87,11 @@ C:
<hr>
<h3>Pythonize () [C++] or initialize () [C]</h3>
<p>
-Constructor/initializer - loads and initializaes the interpreter and actquires the global interpreter lock.
+Constructor/initializer - loads and initializaes the interpreter and acquires the global interpreter lock.
Sets the value of pythonInit to <b>true</b> on success or <b>false</b> if construction/initialization fails
Initializes the global thread state (first instance) or restores the global thread state (second and later
instances). It is the programmer's resposibility to release the global interpreter lock to enable other
-code to access the interpreter. The lock and thread state are automatically actquired when any Pythonize
+code to access the interpreter. The lock and thread state are automatically acquired when any Pythonize
instance is created..
</p>
<hr>
@@ -168,9 +168,9 @@ returns the results of the function call as a PyObject. Returns <b>NULL</b> on f
Releases the global interpreter lock using PyEval_SaveThread. Saves the global thread state.
</p>
<hr>
-<h3>void actquireLock ()</h3>
+<h3>void acquireLock ()</h3>
<p>
-Actquires the global interpreter lock using PyEval_RestoreThread. Restores the global thread state.
+Acquires the global interpreter lock using PyEval_RestoreThread. Restores the global thread state.
</p>
<hr>
<h3>PyThreadState *getThreadState ()</h3>