➜

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.

Author jpe
Recipients BreamoreBoy, asvetlov, jpe, pitrou, r.david.murray, steve.dower, tim.golden, vstinner, zach.ware
Date 2015-04-14.00:52:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428972773.92.0.332301691914.issue14484@psf.upfronthosting.co.za>
In-reply-to
Content 
A problem with os.kill with CTRL_C_EVENT is that CTRL_C_EVENT == 0 and on unix kill w/ a signal number of 0 is how you test to see if a process is running.  This means that code written on unix to see if a process exists will try to send a ctrl-c to the other process; it will fail because GenerateConsoleCtrlEvent is so limited but the error message is likely to be confusing.

Not using the kill() name also means that developers coming from unix won't expect other signal numbers to work.
History
Date User Action Args
2015-04-14 00:52:54jpesetrecipients: + jpe, pitrou, vstinner, tim.golden, r.david.murray, asvetlov, BreamoreBoy, zach.ware, steve.dower
2015-04-14 00:52:53jpesetmessageid: <1428972773.92.0.332301691914.issue14484@psf.upfronthosting.co.za>
2015-04-14 00:52:53jpelinkissue14484 messages
2015-04-14 00:52:53jpecreate