This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Robin.Schreiber
Recipients Robin.Schreiber, belopolsky, loewis, pitrou
Date 2013-08-18.13:17:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Updated patch accordingly. 
Regarding the problem in , it can indeed be solved by returning the already existing module object, if PyInit is called multiple times. I followed the discussion and can not make out a definite decision on how to handle this.
My understanding is, that up to now extension modules are only supposed to be initialized once per interpreter, so the check I have included in, for example issue15651, makes sense from this perspective. There have been reasonable desires (from Eli) to make the module state separate from each imported module within the interpreter, but this would involve more drastic changes and will be rather part of future Python releases.
Should we therefore (for now) make this a mandatory PEP3121 convention and include it into the xxmodule.c refactoring?
Date User Action Args
2013-08-18 13:17:42Robin.Schreibersetrecipients: + Robin.Schreiber, loewis, belopolsky, pitrou
2013-08-18 13:17:42Robin.Schreibersetmessageid: <>
2013-08-18 13:17:42Robin.Schreiberlinkissue15849 messages
2013-08-18 13:17:41Robin.Schreibercreate