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 michael.foord
Recipients Technologov, andersjm, christian.heimes, kap4020, loewis, michael.foord, nnorwitz, tebeka, tim.peters, trent
Date 2010-03-27.13:52:12
SpamBayes Score 0.00058073
Marked as misclassified No
Message-id <>
To make it clear, even though it would be incomplete, a partial implementation of os.kill(...) for Windows would be very useful and provide some level of compatibility with applications that use os.kill (so even if os.kill(...) duplicates functionality in other modules - although that was disputed - it should be provided for compatibility reasons).

An implementation similar to the IronPython one is probably the best that can be managed and would still be useful: accepting only signal.SIGINT and signal.SIGBREAK and first trying Kernel32.GenerateConsoleCtrlEvent, falling back to killing the process.
Date User Action Args
2010-03-27 13:52:15michael.foordsetrecipients: + michael.foord, tim.peters, loewis, nnorwitz, tebeka, andersjm, christian.heimes, kap4020, Technologov, trent
2010-03-27 13:52:14michael.foordsetmessageid: <>
2010-03-27 13:52:12michael.foordlinkissue1220212 messages
2010-03-27 13:52:12michael.foordcreate