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 jpe, steve.dower, tim.golden, zach.ware
Date 2015-04-14.15:24:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
os.kill() on Windows cannot act like it does on non-windows platforms because of differences in the underlying platforms.  I think only kill() with a signal number of 9 (terminate process unconditionally) and a signal number of 0 (test to see if process exists) could be implemented.  It isn't possibly to send the INT signal or a HUP signal to another process -- or at least it isn't possible without the use of questionable api's and code.

Windows specific functions would be added for terminateprocess() and generateconsolectrlevent().  os.kill() on non-windows platforms would be left alone.
Date User Action Args
2015-04-14 15:24:21jpesetrecipients: + jpe, tim.golden, zach.ware, steve.dower
2015-04-14 15:24:21jpesetmessageid: <>
2015-04-14 15:24:21jpelinkissue23948 messages
2015-04-14 15:24:21jpecreate