Message 157424 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Content 
> 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.