[Python-checkins] r45344 - python/trunk/Doc/api/intro.tex (original) (raw)
martin.v.loewis python-checkins at python.org
Thu Apr 13 09:28:29 CEST 2006
- Previous message: [Python-checkins] r45343 - python/trunk/Objects/unicodeobject.c
- Next message: [Python-checkins] r45345 - python/trunk/Modules/_testcapimodule.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Author: martin.v.loewis Date: Thu Apr 13 09:28:29 2006 New Revision: 45344
Modified: python/trunk/Doc/api/intro.tex Log: Stop claiming that Py_Finalize releases all memory. Fixes part of #1445210.
Modified: python/trunk/Doc/api/intro.tex
--- python/trunk/Doc/api/intro.tex (original) +++ python/trunk/Doc/api/intro.tex Thu Apr 13 09:28:29 2006 @@ -572,8 +572,11 @@ Sometimes, it is desirable to ``uninitialize'' Python. For instance, the application may want to start over (make another call to \cfunction{Py_Initialize()}) or the application is simply done with its -use of Python and wants to free all memory allocated by Python. This +use of Python and wants to free memory allocated by Python. This can be accomplished by calling \cfunction{Py_Finalize()}. The function \cfunction{Py_IsInitialized()}\ttindex{Py_IsInitialized()} returns true if Python is currently in the initialized state. More information about these functions is given in a later chapter. +Notice that \cfunction{Py_Finalize} does \emph{not} free all memory +allocated by the Python interpreter, e.g. memory allocated by extension +modules currently cannot be released.
- Previous message: [Python-checkins] r45343 - python/trunk/Objects/unicodeobject.c
- Next message: [Python-checkins] r45345 - python/trunk/Modules/_testcapimodule.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]