Message96395
| Author |
pitrou |
| Recipients |
Rhamphoryncus, bamby, exarkun, gvanrossum, laca, movement, mstepnicki, pitrou, ross |
| Date |
2009年12月14日.19:04:50 |
| SpamBayes Score |
0.00039262758 |
| Marked as misclassified |
No |
| Message-id |
<1260817528.3360.30.camel@localhost> |
| In-reply-to |
<1260816739.78.0.915128917198.issue1975@psf.upfronthosting.co.za> |
| Content |
> 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. |
|