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 flox
Recipients docs@python, flox, rsevcan
Date 2014-04-29.17:16:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398791809.52.0.850759217678.issue21382@psf.upfronthosting.co.za>
In-reply-to
Content
It's about documentation only.

The sentence is not wrong, but it is slightly confusing, and there's no hint which signals are defined on Windows.

"On Windows, signal() can only be called with SIGABRT, SIGFPE, SIGILL, SIGINT, SIGSEGV, or SIGTERM. A ValueError will be raised in any other case."

Reading only this documentation, if the developer doesn't have a test platform on Windows, he could blindly write:

try:
    signal.signal(signal.SIGPIPE, lambda signum, frame: sys.exit(1))
except ValueError:
    pass

... until a Windows user detects the issue (thank you rsevcan)


Now I just found this page which is relevant here ... either we could link to the page in a "See also" section, or give an hint about which signals are defined or not.
http://msdn.microsoft.com/en-us/library/xdkz3x12.aspx
History
Date User Action Args
2014-04-29 17:16:49floxsetrecipients: + flox, docs@python, rsevcan
2014-04-29 17:16:49floxsetmessageid: <1398791809.52.0.850759217678.issue21382@psf.upfronthosting.co.za>
2014-04-29 17:16:49floxlinkissue21382 messages
2014-04-29 17:16:48floxcreate