[issue11380] Improve reporting of broken stdout pipe during interpreter shutdown

[Antoine Pitrou]

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 <report at bugs.python.org>
<http://bugs.python.org/issue11380>
_______________________________________