Antoine Pitrou <pit...@free.fr> added the comment: > The spec broken is here: > > http://docs.python.org/library/signal.html
I would argue it is not broken. This documentation page is about a module of the standard library, it doesn't specify the underlying C implementation. That "the main thread will be the only one to receive signals" is true if you consider it from the Python code's point of view: signal handlers are always called in the main thread, even if the OS-level signal was delivered to (and caught by) another thread. I don't have any strong view over whether the interpreter should, theoretically, block signals in non-main threads. But, practically, blocking signals apparently produced issues with readline (and possibly other libs relying on signals), which is why they are not blocked today. ---------- _______________________________________ 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
