[Import-SIG] New draft revision for PEP 382
pje at telecommunity.com
Sat Jul 9 00:33:23 CEST 2011
At 03:52 PM 7/8/2011 -0600, Eric Snow wrote:
>1. Should this PEP wait until importlib.__import__ replaces the
>builtin __import__? That will have bearing on where the
>implementation takes place. I'm not sure of the status of that
>effort, other than what Brett has reported in the tracker issue
>(http://bugs.python.org/issue2377), nor of the timeframe.
>2. Should it wait for the work on the import engine (a GSOC project).
>It sounds like a PEP is in the works right now. It may also impact
>the implementation of this PEP.
Honestly, since I've done very little with Python 3.x and don't
expect to be involved in the implementation there, I would leave
answering those questions to the folks involved.
I will say, though, that this really doesn't modify the main import
processing loop much; it's just an extra method call at the point
where you have a finder, and a few extra local variables. So I don't
see any insurmountable obstacles to adding it to import.c, at least
given what I remember of how the 2.x version works.
But again, I'm not the one doing the work, so take that with a grain
of salt. ;-)
More information about the Import-SIG