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 exarkun
Recipients Rhamphoryncus, bamby, exarkun, georg.brandl, gvanrossum, laca, movement, mstepnicki, pitrou, ross
Date 2009-12-14.19:14:13
SpamBayes Score 7.24641e-08
Marked as misclassified No
Message-id <>
> >

> I would argue it is not broken.

If it's not broken, then the docs are at least confusing.  They should
make clear whether they are talking about the underlying signal or the
Python signal handler.  This makes a difference for many applications
which deal with signals.  I would even say that due to the very tricky
nature of signals, the documentation *should* be discussing the way it
is implemented.  Without that information, it's very difficult to handle
some situations correctly.  This wouldn't necessarily mean that the
implementation would have to stay the same, either - just that the
implementation be documented for each version (of course, keeping it the
same would be preferable, for all the normal reasons).
Date User Action Args
2009-12-14 19:14:15exarkunsetrecipients: + exarkun, gvanrossum, georg.brandl, Rhamphoryncus, pitrou, movement, ross, bamby, laca, mstepnicki
2009-12-14 19:14:15exarkunsetmessageid: <>
2009-12-14 19:14:14exarkunlinkissue1975 messages
2009-12-14 19:14:13exarkuncreate