A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-October/057275.html below:

[Python-Dev] Assignment to __class__ of module? (Autoloading? (Making Queue.Queue easier to use))

[Python-Dev] Assignment to __class__ of module? (Autoloading? (Making Queue.Queue easier to use)) [Python-Dev] Assignment to __class__ of module? (Autoloading? (Making Queue.Queue easier to use))Josiah Carlson jcarlson at uci.edu
Thu Oct 13 20:13:23 CEST 2005
Eyal Lotem <eyal.lotem at gmail.com> wrote:
> Why not lazily import modules by importing them when they are needed
> (i.e inside functions), and not in the top-level module scope?

Because then it wouldn't be automatic.

The earlier portion of this discussion came from...

    import module
    #module.foo does not reference a module
    module.foo
    #now module.foo references a module

The discussion is about how we can get that kind of behavior.

 - Josiah

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4