Antoine Pitrou <pit...@free.fr> added the comment: > I can't find where we talked about this, maybe just IRC, but that's > there (perhaps poorly) as a special case. > > 0 is 0, but signal.CTRL_C_EVENT is also 0. We try the signal version > first then fall back to TerminateProcess.
Then why set the error? That said, abruptly killing another process and making it return 0 sounds a bit perverted. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14484> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
