[issue1054041] Python doesn't exit with proper resultcode on SIGINT
STINNER Victor
report at bugs.python.org
Tue Feb 19 06:35:52 EST 2019
STINNER Victor <vstinner at redhat.com> added the comment:
> if (PyOS_setsig(SIGINT, SIG_DFL) == SIG_ERR) {
> perror("signal"); /* Impossible in normal environments. */
In my experience, Python is were impossible things happen. Would it be possible to write a better error message to explain what happened?
I expect that if PyOS_setsig() fails, the user cannot do much for that. It may be a bug in the libc and so cannot be fixed easily. Maybe we should simply ignore the error?
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1054041>
_______________________________________
More information about the Python-bugs-list
mailing list