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 pitrou
Recipients BreamoreBoy, amaury.forgeotdarc, aminusfu, benjamin.peterson, christian.heimes, doughellmann, gvanrossum, lakin.wecker, pitrou, titus, ysj.ray
Date 2013-08-18.23:16:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1376867808.19.0.115066838091.issue1257@psf.upfronthosting.co.za>
In-reply-to
Content
I would disagree with this report. There are many errors which are effectively silenced by Python, except for being printed on stderr: for example, errors which occur in a __del__ method or a weakref callback (both of which semantically similar to an atexit handler); but also exceptions which terminate a non-main thread.

Python's error code is derived from the return status of the main thread of execution, not counting any kinds of asynchronous exceptions, which are simply displayed and then ignored.

If you want to write a test for errors at program exit, you should check for stderr's contents (by capturing it).
History
Date User Action Args
2013-08-18 23:16:48pitrousetrecipients: + pitrou, gvanrossum, amaury.forgeotdarc, titus, aminusfu, christian.heimes, lakin.wecker, benjamin.peterson, doughellmann, ysj.ray, BreamoreBoy
2013-08-18 23:16:48pitrousetmessageid: <1376867808.19.0.115066838091.issue1257@psf.upfronthosting.co.za>
2013-08-18 23:16:48pitroulinkissue1257 messages
2013-08-18 23:16:47pitroucreate