bpo-36829: sys.excepthook and sys.unraisablehook flush by vstinner · Pull Request #13620 · python/cpython (original) (raw)

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation0 Commits1 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

sys.excepthook() and sys.unraisablehook() now explicitly flush the
file (usually sys.stderr).

If file.flush() fails, sys.excepthook() silently ignores the error,
whereas sys.unraisablehook() logs the new exception.

https://bugs.python.org/issue36829

vstinner changed the titlebpo-36829: sys.unraisablehook() explicits flush stderr bpo-36829: sys.excepthook and sys.unraisablehook flush

May 28, 2019

sys.excepthook() and sys.unraisablehook() now explicitly flush the file (usually sys.stderr).

If file.flush() fails, sys.excepthook() silently ignores the error, whereas sys.unraisablehook() logs the new exception.

DinoV pushed a commit to DinoV/cpython that referenced this pull request

Jan 14, 2020

sys.excepthook() and sys.unraisablehook() now explicitly flush the file (usually sys.stderr).

If file.flush() fails, sys.excepthook() silently ignores the error, whereas sys.unraisablehook() logs the new exception.