caught in the import web again
Ian Kelly
ian.g.kelly at gmail.com
Mon Nov 17 17:52:32 EST 2014
More information about the Python-list mailing list
Mon Nov 17 17:52:32 EST 2014
- Previous message (by thread): caught in the import web again
- Next message (by thread): caught in the import web again
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Nov 17, 2014 at 3:17 PM, Dave Angel <davea at davea.name> wrote: > "Charles T. Smith" <cts.private.yahoo at gmail.com> Wrote in message: > >> Well, I guess that's the definitive answer... the tips for delaying >> import are good, I'll try to leverage them. >> >> I was hoping there would be a way to have python postpone evaluation >> similar to C's forward references. >> > > In a module that might get tangled in a cycle, avoid global code > that depends on other modules. Instead of putting such > initialization at top level, put inside a function that gets > called after all suspect imports are completed. (That function > has global keywords ). If the problem is that one of those modules would import the current module, then "after all suspect imports are completed" basically means after the current module has finished importing. So what would be responsible for calling such a function?
- Previous message (by thread): caught in the import web again
- Next message (by thread): caught in the import web again
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list