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 Jeremy.Fishman, ncoghlan, pitrou, terry.reedy, ulidtko
Date 2013-09-23.23:05:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379977553.2494.8.camel@fsol>
In-reply-to <>
> 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.

How would you improve it?
Date User Action Args
2013-09-23 23:05:56pitrousetrecipients: + pitrou, terry.reedy, ncoghlan, ulidtko, Jeremy.Fishman
2013-09-23 23:05:55pitroulinkissue11380 messages
2013-09-23 23:05:55pitroucreate