[Python-Dev] requirements for moving __import__ over to importlib?

Robert Kern robert.kern at gmail.com
Thu Feb 9 23:34:25 CET 2012


On 2/9/12 10:15 PM, Antoine Pitrou wrote:
> On Thu, 9 Feb 2012 17:00:04 -0500
> PJ Eby<pje at telecommunity.com>  wrote:
>> On Thu, Feb 9, 2012 at 2:53 PM, Mike Meyer<mwm at mired.org>  wrote:
>>
>>> For those of you not watching -ideas, or ignoring the "Python TIOBE
>>> -3%" discussion, this would seem to be relevant to any discussion of
>>> reworking the import mechanism:
>>>
>>> http://mail.scipy.org/pipermail/numpy-discussion/2012-January/059801.html
>>>
>>> Interesting.  This gives me an idea for a way to cut stat calls per
>> sys.path entry per import by roughly 4x, at the cost of a one-time
>> directory read per sys.path entry.
>
> Why do you even think this is a problem with "stat calls"?

All he said is that reading about that problem and its solution gave him an idea 
about dealing with stat call overhead. The cost of stat calls has demonstrated 
itself to be a significant problem in other, more typical contexts.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
  that is made terrible by our own mad attempt to interpret it as though it had
  an underlying truth."
   -- Umberto Eco



More information about the Python-Dev mailing list