[Python-Dev] requirements for moving import over to importlib? (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Thu Feb 9 23:15:30 CET 2012
- Previous message: [Python-Dev] requirements for moving __import__ over to importlib?
- Next message: [Python-Dev] requirements for moving __import__ over to importlib?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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"?
- Previous message: [Python-Dev] requirements for moving __import__ over to importlib?
- Next message: [Python-Dev] requirements for moving __import__ over to importlib?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]