Message157429
| 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 |
<1333465667.21.0.443606973017.issue14484@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年04月03日 15:07:47 | r.david.murray | set | recipients:
+ r.david.murray, pitrou, tim.golden, brian.curtin, asvetlov |
| 2012年04月03日 15:07:47 | r.david.murray | set | messageid: <1333465667.21.0.443606973017.issue14484@psf.upfronthosting.co.za> |
| 2012年04月03日 15:07:46 | r.david.murray | link | issue14484 messages |
| 2012年04月03日 15:07:46 | r.david.murray | create |
|