RetroSearch Browse

Thu Jul 29 05:53:55 CEST 2004 · https://mail.python.org/pipermail/python-dev/2004-July/046527.html

> OTOH, ensuring that if *any* exception is thrown when importing a
> module, it will not appear in sys.modules (and the exception is raised
> each time you try to import) is IMO a very useful property, and I
> think would solve what I think is Jim's issue at the root.

It's going to be difficult to ensure that nothing ever gets a
reference to a broken module, because of circular imports.  Suppose A
imports B, which imports A. If A's initialisation subsequently fails,
then even if A is removed from sys.modules, B still contains a
reference to the broken A.

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
greg at cosc.canterbury.ac.nz	   +--------------------------------------+

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

Showing content from https://mail.python.org/pipermail/python-dev/2004-July/046527.html below:

[Python-Dev] Fix import errors to have data