RetroSearch Browse

Wed Jul 15 14:39:31 CEST 2009 · https://mail.python.org/pipermail/python-dev/2009-July/090640.html

2009/7/15 Brett Cannon <brett at python.org>:
> I implemented get_filename() as specified in PEP 302 for importlib's source
> and bytecode loaders and I was starting to create the ABC for importlib.abc,
> but then I realized that perhaps the loader should live in runpy instead of
> importlib.
> Putting the new ABC in importlib keeps all PEP 302 ABCs in a single spot.
> But this addition to the PEP 302 protocols is very specific to runpy and is
> not directly required to make imports work (the implementation was just a
> reshuffling of pre-existing code from one method to another). I am tempted
> to leave the ABC out of importlib and stop at implementing get_filename()
> for importlib.abc.PyLoader and PyPycLoader.
> Any opinions?

importlib.

In my view, all of the interfaces defined by PEP 302 should be
available from one place. And importlib is that place.

Paul.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2009-July/090640.html below:

[Python-Dev] Add an ExecutionLoader abc to importlib or to runpy?