Charles-François Natali <neolo...@free.fr> added the comment: >> I agree with Martin: we really do handle the signal, and as such, the >> only way to convey the relevant information to the parent as to which >> signal caused the exit would be to re-raise it, which is really ugly >> and probably not a good idea. > > Why would it be ugly? faulthandler does exactly that.
Because calling exit() is the right way to end a process. For example, it does the following: - atexit()-registered finalizers are run - stdio streams are flushed and closed (although it could probably done by the interpreter) - files created with tmpfile() are removed (on POSIX systems, they're removed after creation, but you can imagine an implementation where they would need to be explicitely removed upon close) This would not be performed if the signal is raised. Since the user has the possibility of restoring default signal handlers with SIG_DFL, I think we could stcik with the current behavior. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14229> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
