Message96391
| Author |
pitrou |
| Recipients |
Rhamphoryncus, bamby, exarkun, gvanrossum, laca, movement, mstepnicki, pitrou, ross |
| Date |
2009年12月14日.18:48:18 |
| SpamBayes Score |
3.761355e-06 |
| Marked as misclassified |
No |
| Message-id |
<1260816535.3360.21.camel@localhost> |
| In-reply-to |
<1260815700.09.0.158850247427.issue1975@psf.upfronthosting.co.za> |
| Content |
> You forget that the original report is about ctrl-C. Should we abandon
> support of it for threaded programs?
We haven't abandoned support, have we? Where is the spec that is
currently broken?
Besides, as Jean-Paul pointed out, the user can now setup a file
descriptor on which a byte will be written out as soon as a signal gets
caught.
> Close as won't-fix?
It is one possibility indeed.
We could also add an API (or an optional argument to the existing APIs)
to block signals in threads created by Python. |
|