This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, sbt, serhiy.storchaka, techtonik
Date 2012-12-19.20:23:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355948602.04.0.73881084109.issue16718@psf.upfronthosting.co.za>
In-reply-to
Content
OK, found the difference between 3.2 and 3.3:
The ImportError exception is still alive when atexit handlers are called, with its __traceback__, and all local variables in Python frames.
And since 3.3 the import system is built with Python functions...

More exactly, I could find the incomplete 'wow' module in sys.last_value.__traceback__.tb_next.tb_frame.f_back.f_back.f_back.f_locals['module']

But all this is not really related to the current issue.
Things should be better in the future, when modules are cleared with true garbage collection.
History
Date User Action Args
2012-12-19 20:23:22amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, techtonik, sbt, serhiy.storchaka
2012-12-19 20:23:22amaury.forgeotdarcsetmessageid: <1355948602.04.0.73881084109.issue16718@psf.upfronthosting.co.za>
2012-12-19 20:23:22amaury.forgeotdarclinkissue16718 messages
2012-12-19 20:23:21amaury.forgeotdarccreate