[Python-Dev] Pre-PEP: Redesigning extension modules (original) (raw)
Eric Snow ericsnowcurrently at gmail.com
Fri Sep 6 07:52:40 CEST 2013
- Previous message: [Python-Dev] Pre-PEP: Redesigning extension modules
- Next message: [Python-Dev] Completing the email6 API changes.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Aug 31, 2013 at 1:16 PM, Stefan Behnel <stefan_ml at behnel.de> wrote:
Nick Coghlan, 31.08.2013 18:49: > This is actually my primary motivation for trying to improve the > "can this be reloaded or not?" aspects of the loader API in PEP 451.
I assume you mean that the extension module would be able to clearly signal that it can't be reloaded, right? I agree that that's helpful. If you're wrapping a C library, then the way that library is implemented might simply force you to prevent any attempts at reloading the wrapper module. But if reloading is possible at all, it would be even more helpful if we could make it really easy to properly support it.
When loader.exec_module() gets called, it should raise ImportError if the module does not support reloading.
-eric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130905/2522477b/attachment.html>
- Previous message: [Python-Dev] Pre-PEP: Redesigning extension modules
- Next message: [Python-Dev] Completing the email6 API changes.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]