[issue20125] We need a good replacement for direct use of load_module(), post-PEP 451

2020-03-18 Thread Brett Cannon
Brett Cannon added the comment: I don't think this is still needed as the importlib docs now has enough examples to show people how to get to get similar results with a few method calls. -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed

[issue20125] We need a good replacement for direct use of load_module(), post-PEP 451

2014-01-06 Thread Eric Snow
Eric Snow added the comment: Yeah, waiting on this until 3.5 is fine with me. Arfrever brought it up so I at least wanted to track it. -- stage: - needs patch versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org

[issue20125] We need a good replacement for direct use of load_module(), post-PEP 451

2014-01-05 Thread Brett Cannon
Brett Cannon added the comment: I say just be patient and wait. No need to rush this as load_module() is still allowed to exist and be used. And if I manage to create SpecLoader than even new-fangled loaders and get load_module() for free. -- ___

[issue20125] We need a good replacement for direct use of load_module(), post-PEP 451

2014-01-04 Thread Eric Snow
New submission from Eric Snow: In issue #19713, it came up that while PEP 451 deprecated Loader.load_module(), it did not provide a suitable replacement for calling it directly. We've worked around this in the stdlib by making calls to private APIs, but that won't work so well for the

[issue20125] We need a good replacement for direct use of load_module(), post-PEP 451

2014-01-04 Thread Eric Snow
Changes by Eric Snow ericsnowcurren...@gmail.com: -- nosy: +larry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20125 ___ ___ Python-bugs-list