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 asvetlov
Recipients asvetlov, brian.curtin, r.david.murray
Date 2012-04-03.15:09:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333465759.12.0.217423729526.issue14480@psf.upfronthosting.co.za>
In-reply-to
Content
There are no `kill` function in Windows API.
From my perspective win32_kill was added to emulate posix sibling if possible. If not — better to give another Windows native name to that function.
Really don't see good solution. Maybe better what we can do — declare what os.kill cannot be called with 0 signum on Windows for proc presence checking and note that fact in os.rst.
Terminating process looks like overcomplication. POSIX kill only sends signal to process and nothing more.
History
Date User Action Args
2012-04-03 15:09:19asvetlovsetrecipients: + asvetlov, r.david.murray, brian.curtin
2012-04-03 15:09:19asvetlovsetmessageid: <1333465759.12.0.217423729526.issue14480@psf.upfronthosting.co.za>
2012-04-03 15:09:18asvetlovlinkissue14480 messages
2012-04-03 15:09:18asvetlovcreate