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 wrwrwr
Recipients docs@python, paul.moore, steve.dower, tim.golden, wrwrwr, zach.ware
Date 2016-11-18.19:38:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479497916.69.0.534558560438.issue28738@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-11-18 19:38:36wrwrwrsetrecipients: + wrwrwr, paul.moore, tim.golden, docs@python, zach.ware, steve.dower
2016-11-18 19:38:36wrwrwrsetmessageid: <1479497916.69.0.534558560438.issue28738@psf.upfronthosting.co.za>
2016-11-18 19:38:36wrwrwrlinkissue28738 messages
2016-11-18 19:38:36wrwrwrcreate