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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, loewis, scoder
Date 2011-11-18.20:31:11
SpamBayes Score 6.8756674e-07
Marked as misclassified No
Message-id <>
> ... and the module init function could create and register a
> different module first, and ...
Actually, this *does* happen, the PIL module is written this way.
And I don't agree with the "best effort" argument.  If there is a slight chance that this does not work, we'll have to fix it sooner or later.

But please check this import lock thing: if _PyImport_AcquireLock and _PyImport_ReleaseLock are always called around extension module initialization, then we don't have to worry about other threads; and nested calls are already handled by the "oldimportcontext" variable in your patch.
Date User Action Args
2011-11-18 20:31:12amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, loewis, scoder
2011-11-18 20:31:12amaury.forgeotdarcsetmessageid: <>
2011-11-18 20:31:11amaury.forgeotdarclinkissue13429 messages
2011-11-18 20:31:11amaury.forgeotdarccreate