On Thu, Feb 9, 2012 at 13:43, PJ Eby <p...@telecommunity.com> wrote:
> > On Feb 9, 2012 9:58 AM, "Brett Cannon" <br...@python.org> wrote: > > This actually depends on the type of ImportError. My current solution > actually would trigger an ImportError at the import statement if no finder > could locate the module. But if some ImportError was raised because of some > other issue during load then that would come up at first use. > > That's not really a lazy import then, or at least not as lazy as what > Mercurial or PEAK use for general lazy importing. If you have a lot of > them, that module-finding time really adds up. > > Again, the goal is fast startup of command-line tools that only use a > small subset of the overall framework; doing disk access for lazy imports > goes against that goal. > Depends if you consider stat calls the overhead vs. the actual disk read/write to load the data. Anyway, this is going to lead down to a discussion/argument over design parameters which I'm not up to having since I'm not actively working on a lazy loader for the stdlib right now.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
