Antoine Pitrou added the comment: > I'm not sure that we always want to exit on CTRL-c.
That's what the forkserver does right now, it's just that it does it with a traceback that's useless to the user. > Maybe ignore it, but be killed when its master gets a CTRL-c? That's a possibility (the forkserver should already exit automatically when its parent dies), the problem is what to do for the forkserver's children? Should they restore the default signal handler? Simply silencing the KeyboardInterrupt traceback at least is a straightforward solution with little risk of side effects. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30185> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
