Comments on: Automatic Python imports with autoimp, lazy ones with Importing

By: Tim Lesher

Tim Lesher — Wed, 21 Jun 2006 19:09:22 +0000

Wow. My first blog post ever was a wish for just this:

http://apipes.blogspot.com/2004_08_01_apipes_archive.html

By: Jay

Jay — Tue, 13 Jun 2006 02:23:13 +0000

Are there any drawbacks to doing this?

By: import this. » Blog Archive » Dynamic module loading

import this. » Blog Archive » Dynamic module loading — Mon, 12 Jun 2006 23:24:17 +0000

[...] Kevin Dangoor metions dynamic module loading: …Phillip Eby just released Importing which provides dynamic module loading (it also provides “load object Y from module X specified in python dotted notation string�? utility functions, which could eliminate a utility we have in tg.util.) [...]

By: Connelly Barnes

Connelly Barnes — Mon, 12 Jun 2006 23:23:14 +0000

Neither autoimp nor Importing puts the imported modules in __builtins__. Instead, the imported, wrapped modules are typically placed in the caller’s globals().

The module autoimp was originally intended to automatically import all modules at the interactive prompt, and thus save the user from typing “py.std.*” or “import os, sys, urllib2, collections, bz2, zlib, …” The lazyModule class in Philip Eby’s Importing module loads a single module, instead of all modules. Thus the following are roughly equivalent:

>>> from autoimp import a, b, c

>>> a = lazyModule(‘a’)
>>> b = lazyModule(‘b’)
>>> c = lazyModule(‘c’)

By: Ian Bicking

Ian Bicking — Mon, 12 Jun 2006 16:57:21 +0000

I think the motivation is good, but py.std (http://codespeak.net/py/current/doc/misc.html#the-py-std-hook or I wrote about it here: http://blog.ianbicking.org/py-std.html) serves a similar purpose, and is more explicit. The implementation is trivial. Putting it in __builtins__ is a little more controversial.