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, pitrou
Date 2009-12-01.16:59:42
SpamBayes Score 5.3395198e-08
Marked as misclassified No
Message-id <1259686784.62.0.556695652783.issue7317@psf.upfronthosting.co.za>
In-reply-to
Content
Seconded. 
But such messages are also printed when the interpreter exits, when
poorly written __del__ methods access already disposed modules. Raising
a full traceback could cause users to think that the error is more
severe than it is.

Is there an already existing flag that could control this behaviour?
Otherwise, well, just ignore my remark.
History
Date User Action Args
2009-12-01 16:59:44amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, pitrou
2009-12-01 16:59:44amaury.forgeotdarcsetmessageid: <1259686784.62.0.556695652783.issue7317@psf.upfronthosting.co.za>
2009-12-01 16:59:43amaury.forgeotdarclinkissue7317 messages
2009-12-01 16:59:42amaury.forgeotdarccreate