[issue23642] Interaction of ModuleSpec and C Extension Modules

Change by Petr Viktorin : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue23642] Interaction of ModuleSpec and C Extension Modules

Petr Viktorin added the comment: ping; this issue can be closed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23642 ___ ___ Python-bugs-list

[issue23642] Interaction of ModuleSpec and C Extension Modules

Petr Viktorin added the comment: Since PEP 489 (Python 3.5.0b1), loaders now support create_module/exec_module. For modules which don't use the PEP's new multi-phase init mechanism (which is most of them, currently), load_module() does all the work and exec_module is a no-op. So, this issue

[issue23642] Interaction of ModuleSpec and C Extension Modules

Changes by Raúl Cumplido raulcumpl...@gmail.com: -- nosy: +raulcd ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23642 ___ ___ Python-bugs-list

[issue23642] Interaction of ModuleSpec and C Extension Modules

Changes by Stefan Behnel sco...@users.sourceforge.net: -- nosy: +scoder ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23642 ___ ___

[issue23642] Interaction of ModuleSpec and C Extension Modules

Nick Coghlan added the comment: Added Petr to the nosy list here as well. Petr - this is the kind of discrepancy I'm hoping that PEP 489 can help remedy, so it may make for a good test case :) -- nosy: +encukou ___ Python tracker

[issue23642] Interaction of ModuleSpec and C Extension Modules

Brett Cannon added the comment: The PEP is now live: https://www.python.org/dev/peps/pep-0489/ . If you want to participate in the discussion it will probably happen on the import-sig. -- ___ Python tracker rep...@bugs.python.org

[issue23642] Interaction of ModuleSpec and C Extension Modules

David Beazley added the comment: Note: Might be related to Issue 19713. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23642 ___ ___

[issue23642] Interaction of ModuleSpec and C Extension Modules

Brett Cannon added the comment: There is a proposed PEP on the import-sig: https://mail.python.org/pipermail/import-sig/2015-March/000904.html . I'm hoping to add it for the author to the PEP index on Friday. Basically we punted on extension modules as we ran out of time in Python 3.4.

[issue23642] Interaction of ModuleSpec and C Extension Modules

David Beazley added the comment: This is great news. Read the PEP draft and think this is a very good thing to be addressing. Thanks, Brett. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23642

[issue23642] Interaction of ModuleSpec and C Extension Modules

David Beazley added the comment: inal comment. It seems that one can generally avoid a lot of nastiness if importlib.reload() is used instead. For example: mod = sys.modules[spec.name] = module_from_spec(spec) importlib.reload(mod) This works for both source and Extension modules and

[issue23642] Interaction of ModuleSpec and C Extension Modules

Changes by Berker Peksag berker.pek...@gmail.com: -- nosy: +brett.cannon, eric.snow, ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23642 ___

[issue23642] Interaction of ModuleSpec and C Extension Modules

David Beazley added the comment: Sorry. I take back the previous message. It still doesn't quite do what I want. Anyways, any insight or thoughts about this would be appreciated ;-). -- ___ Python tracker rep...@bugs.python.org

[issue23642] Interaction of ModuleSpec and C Extension Modules

New submission from David Beazley: I have been investigating some of the new importlib machinery and the addition of ModuleSpec objects. I am a little curious about the intended handling of C Extension modules going forward. Backing up for a moment, consider a pure Python module. It seems