➜

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 Jeremy.Fishman, ncoghlan, pitrou, terry.reedy, ulidtko
Date 2013-09-23.23:03:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7efGYQgeetgrfuzcCg-L9vDsGocVObJtbLcStj6qFBg9g@mail.gmail.com>
In-reply-to <1379966304.03.0.500286721025.issue11380@psf.upfronthosting.co.za>
Content 
My specific suggestion was aimed at 3.4 - I think reporting the failure to
flush stdout on stderr is the right thing to do (since data may have been
lost and people can suppress it by closing stdout early, including in an
atexit handler), but I also think it's worth improving the error message in
the specific case of a broken pipe error.

However, I also agree the error output is more wrong in 2.7, so improving
that would be good, too.
History
Date User Action Args
2013-09-23 23:03:21ncoghlansetrecipients: + ncoghlan, terry.reedy, pitrou, ulidtko, Jeremy.Fishman
2013-09-23 23:03:21ncoghlanlinkissue11380 messages
2013-09-23 23:03:21ncoghlancreate