Jean-Paul Calderone <exar...@divmod.com> added the comment: > > http://docs.python.org/library/signal.html
> 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). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1975> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
