Retitle, clarifying that the PEP talks about
extension modules.
This commit is contained in:
parent
a4f91773f4
commit
1ccd48940d
12
pep-3121.txt
12
pep-3121.txt
|
@ -1,5 +1,5 @@
|
|||
PEP: 3121
|
||||
Title: Module Initialization and finalization
|
||||
Title: Extension Module Initialization and Finalization
|
||||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Martin v. Löwis <martin@v.loewis.de>
|
||||
|
@ -13,11 +13,11 @@ Post-History:
|
|||
Abstract
|
||||
========
|
||||
|
||||
Module initialization currently has a few deficiencies. There is no
|
||||
cleanup for modules, the entry point name might give naming conflicts,
|
||||
the entry functions don't follow the usual calling convention, and
|
||||
multiple interpreters are not supported well. This PEP addresses these
|
||||
issues.
|
||||
Extension module initialization currently has a few deficiencies.
|
||||
There is no cleanup for modules, the entry point name might give
|
||||
naming conflicts, the entry functions don't follow the usual calling
|
||||
convention, and multiple interpreters are not supported well. This PEP
|
||||
addresses these issues.
|
||||
|
||||
Problems
|
||||
========
|
||||
|
|
Loading…
Reference in New Issue