Re: How best to replace imp.load_module()?

Keep in mind I already need a fair bit of this kind of thing to make runpy
work properly.

Moving that infrastructure to importlib.util is worthwhile, because it
makes it easier to evolve the core import implementation with confidence
that we're not breaking even obscure use cases.

The migration of extension modules to PEP 451 should take place on the road
to 3.5, and we should take a close look at migrating pdb and friends to
runpy with a view to adding -m support (which may require new features in
runpy itself).

Moving zipimport to a frozen Python module may also be desirable.

I think that's a better use case driven path to follow, and we can hold off
on finalising the imp.load_module deprecation for the time being.

Cheers,
Nick.

_______________________________________________
Import-SIG mailing list
[email protected]
https://mail.python.org/mailman/listinfo/import-sig