diff options
| author | Fred Drake <fdrake@acm.org> | 2004-02-17 04:17:36 (GMT) |
|---|---|---|
| committer | Fred Drake <fdrake@acm.org> | 2004-02-17 04:17:36 (GMT) |
| commit | 70a30e8c948e2cad90f8e49e7771059c930ec61e (patch) | |
| tree | 22a3d61b3298889a83534ded3070a039a50347b0 /Doc/api | |
| parent | 5d7c06720dcdc61fd96b5c30bff798849a53cad5 (diff) | |
| download | cpython-70a30e8c948e2cad90f8e49e7771059c930ec61e.zip cpython-70a30e8c948e2cad90f8e49e7771059c930ec61e.tar.gz cpython-70a30e8c948e2cad90f8e49e7771059c930ec61e.tar.bz2 | |
markup correction
Diffstat (limited to 'Doc/api')
| -rw-r--r-- | Doc/api/newtypes.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/api/newtypes.tex b/Doc/api/newtypes.tex index 5b2e6cf..1490eed 100644 --- a/Doc/api/newtypes.tex +++ b/Doc/api/newtypes.tex @@ -1396,7 +1396,7 @@ might be collected by a garbage collection on any thread). This is not a problem for Python API calls, since the thread on which tp_dealloc is called will own the Global Interpreter Lock (GIL). However, if the object being destroyed in turn destroys objects from -some other C or C++ library, care should be taken to ensure that +some other C or \Cpp{} library, care should be taken to ensure that destroying those objects on the thread which called tp_dealloc will not violate any assumptions of the library. |