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 r.david.murray
Recipients asvetlov, brian.curtin, pitrou, r.david.murray, tim.golden
Date 2012-04-03.15:07:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I would think that if Windows doesn't support a specific signal, os.kill should raise a ValueError.  But I'm an outsider here, I know nothing about how Windows works for this except what I'm reading here.  

To answer your question: there are many reasons to call kill on unix, and only a few of them kill the process.  Kill is just an historical name, it really means 'send a signal'.

In a broader picture, I think that os.kill calls should have the same "meaning", insofar as possible, on both linux and windows.  Having a single API with the same syntax but different semantics on different platforms sounds bad to me.
Date User Action Args
2012-04-03 15:07:47r.david.murraysetrecipients: + r.david.murray, pitrou, tim.golden, brian.curtin, asvetlov
2012-04-03 15:07:47r.david.murraysetmessageid: <>
2012-04-03 15:07:46r.david.murraylinkissue14484 messages
2012-04-03 15:07:46r.david.murraycreate