[Python-Dev] Fix import errors to have data (original) (raw)

Phillip J. Eby pje at telecommunity.com
Mon Aug 2 04:44:18 CEST 2004

At 01:37 PM 8/2/04 +1200, Greg Ewing wrote:

> > Circular imports, to be made consistent, would need > > something like a final "commit" after all imports succeeded. > > Silly idea. Typically, circular imports aren't planned, they just > happen, and (usually) just happen to work.

I thought Christian meant this was something that would be done automatically, not something the user would have to do explicitly. Maybe it could be as simple as saving a snapshot of sys.modules whenever importing of a module is begun, and if execution of its body doesn't complete, restoring the snapshot?

That might be over-cautious. It's probably safe to keep modules whose body code executed without error.

More information about the Python-Dev mailing list