Message 261852 - Python tracker

➜

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	ncoghlan
Recipients	benjamin.peterson, gjb1002, gvanrossum, ncoghlan, pitrou, pjenvey, stutzbach, terry.reedy
Date	2016-03-16.12:57:02
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1458133022.8.0.474910435453.issue13601@psf.upfronthosting.co.za>
In-reply-to

Content
This question came up today in the context of the final line of a traceback output potentially being missing from stderr if the closing flush of the standard streams is missed for any reason. That's not going to be a common scenario (as far as I know it was an entirely hypothetical discussion), but the last line of a traceback is the one with the actual error message, so it's likely to be annoyingly cryptic if it does happen.

This question came up today in the context of the final line of a traceback output potentially being missing from stderr if the closing flush of the standard streams is missed for any reason.

That's not going to be a common scenario (as far as I know it was an entirely hypothetical discussion), but the last line of a traceback is the one with the actual error message, so it's likely to be annoyingly cryptic if it does happen.

History
Date	User	Action	Args
2016-03-16 12:57:03	ncoghlan	set	recipients: + ncoghlan, gvanrossum, terry.reedy, gjb1002, pitrou, pjenvey, benjamin.peterson, stutzbach
2016-03-16 12:57:02	ncoghlan	set	messageid: <1458133022.8.0.474910435453.issue13601@psf.upfronthosting.co.za>
2016-03-16 12:57:02	ncoghlan	link	issue13601 messages
2016-03-16 12:57:02	ncoghlan	create