[Python-checkins] r55089 - peps/trunk/pep-3121.txt
martin.v.loewis
python-checkins at python.org
Thu May 3 09:01:16 CEST 2007
Author: martin.v.loewis
Date: Thu May 3 09:01:14 2007
New Revision: 55089
Modified:
peps/trunk/pep-3121.txt
Log:
C module -> extension module.
Modified: peps/trunk/pep-3121.txt
==============================================================================
--- peps/trunk/pep-3121.txt (original)
+++ peps/trunk/pep-3121.txt Thu May 3 09:01:14 2007
@@ -25,13 +25,13 @@
Module Finalization
-------------------
-Currently, C modules are initialized usually once and then "live"
-forever. The only exception is when Py_Finalize() is called: then
-the initialization routine is invoked a second time. This is bad
+Currently, extension modules are initialized usually once and then
+"live" forever. The only exception is when Py_Finalize() is called:
+then the initialization routine is invoked a second time. This is bad
from a resource management point of view: memory and other resources
-might get allocated each time initialization is called, but there
-is no way to reclaim them. As a result, there is currently no
-way to completely release all resources Python has allocated.
+might get allocated each time initialization is called, but there is
+no way to reclaim them. As a result, there is currently no way to
+completely release all resources Python has allocated.
Entry point name conflicts
--------------------------
More information about the Python-checkins
mailing list