[issue21382] Signal module doesnt raises ValueError Exception

Changes by Berker Peksag : -- nosy: +berker.peksag resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.6 -Python 3.4 ___ Python tracker

[issue21382] Signal module doesnt raises ValueError Exception

Roundup Robot added the comment: New changeset 1fcf68e6f4c7 by Berker Peksag in branch '3.5': Issue #21382: Clarify signal.signal() documentation on Windows https://hg.python.org/cpython/rev/1fcf68e6f4c7 New changeset 3e27b21e3a7d by Berker Peksag in branch 'default': Issue #21382: Clarify

[issue21382] Signal module doesnt raises ValueError Exception

Tim Golden added the comment: To be honest I can't get excited about this one. The only sensible change is to remove the rather specific comment about ValueError and just leave the fact that only certain signals are valid. Because the C code defines module-level constants on the basis of

[issue21382] Signal module doesnt raises ValueError Exception

New submission from rsevcan: signal.signal() built-in function doesnt throws a ValueError exception in Windows when is called with a different signal than SIGABRT, SIGFPE, SIGILL, SIGINT, SIGSEGV, or SIGTERM, as it is written in the documentation.

[issue21382] Signal module doesnt raises ValueError Exception

Changes by Florent Xicluna florent.xicl...@gmail.com: -- components: +Library (Lib), Windows nosy: +flox type: enhancement - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21382 ___

[issue21382] Signal module doesnt raises ValueError Exception

Florent Xicluna added the comment: 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