[New-bugs-announce] [issue28738] Document SIGBREAK as argument for signal() under Windows.

[Wojtek Ruszczewski]

New submission from Wojtek Ruszczewski:

SIGBREAK should be listed as acceptable for signal.signal() under Windows.

Some context. Registering a handler for SIGBREAK may be useful as this is the signal that generating CTRL_BREAK_EVENT results in (and the latter combined with the CREATE_NEW_PROCESS_GROUP flag might be the closest that one can get to terminating a process group).

Some pointers:
* The changed documentation fragment: https://docs.python.org/3/library/signal.html#signal.signal.
* MSDN doesn't say so much about SIGBREAK: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682541(v=vs.85).aspx.
* SIGBREAK was added to the signal module with #466877.
* The signal number check looks as follows: https://github.com/python/cpython/blob/3.6/Modules/signalmodule.c#L402.

----------
assignee: docs at python
components: Documentation, Windows
files: sigbreak.patch
keywords: patch
messages: 281159
nosy: docs at python, paul.moore, steve.dower, tim.golden, wrwrwr, zach.ware
priority: normal
severity: normal
status: open
title: Document SIGBREAK as argument for signal() under Windows.
type: enhancement
versions: Python 3.7
Added file: http://bugs.python.org/file45538/sigbreak.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28738>
_______________________________________