Antoine Pitrou added the comment: > 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? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11380> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
