[issue14480] os.kill on Windows should accept zero as signal

STINNER Victor added the comment: > 0 has no special meaning on Windows so I'd rather not add another special > case for posix emulation. Additionally, 0 unfortunately already means two > things as it is: signal.CTRL_C_EVENT and the int 0. I agree, it's not a good idea to support os.kill(pid,

[issue14480] os.kill on Windows should accept zero as signal

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue14480] os.kill on Windows should accept zero as signal

Andrew Svetlov added the comment: 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 — dec

[issue14480] os.kill on Windows should accept zero as signal

Brian Curtin added the comment: I meant that in the underlying, such as in the TerminateProcess API, 0 doesn't mean anything special. As is being debated over on #14484 we currently take all integers to be passed to TerminateProcess (the int becomes the killed proc's return code), and two sig

[issue14480] os.kill on Windows should accept zero as signal

R. David Murray added the comment: Hmm. I would think it would be a good idea to have os.kill do posix emulation where that makes sense, it makes cross-platform usage easier. That's what 'kill' with no signal does, right (kills the process, just like the posix default)? The posix spec says

[issue14480] os.kill on Windows should accept zero as signal

Brian Curtin added the comment: -1 0 has no special meaning on Windows so I'd rather not add another special case for posix emulation. Additionally, 0 unfortunately already means two things as it is: signal.CTRL_C_EVENT and the int 0. -- status: open -> pending _

[issue14480] os.kill on Windows should accept zero as signal

Changes by R. David Murray : -- nosy: +brian.curtin stage: -> needs patch type: behavior -> enhancement ___ Python tracker ___ ___ Py

[issue14480] os.kill on Windows should accept zero as signal

New submission from Andrew Svetlov : Starting from 3.2 Python supports os.kill for Windows. It process signal.CTRL_C_EVENT and signal.CTRL_BREAK_EVENT, and kills pid for all other signals. Posix allows to pass zero signal to check pid for existing. It will be nice to keep that behavior for Wind