➜

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 Rhamphoryncus
Recipients Rhamphoryncus, bamby, exarkun, gvanrossum, laca, movement, mstepnicki, pitrou, ross
Date 2009-12-14.18:34:58
SpamBayes Score 0.0005143402
Marked as misclassified No
Message-id <1260815700.09.0.158850247427.issue1975@psf.upfronthosting.co.za>
In-reply-to
Content 
You forget that the original report is about ctrl-C.  Should we abandon
support of it for threaded programs?  Close as won't-fix?

We could also just block SIGINT, but why?  That means we don't support
python signal handlers in threaded programs (signals sent to the
process, not ones sent direct to threads), and IMO threads expecting a
specific signal should explicitly unblock it anyway.
History
Date User Action Args
2009-12-14 18:35:00Rhamphoryncussetrecipients: + Rhamphoryncus, gvanrossum, exarkun, pitrou, movement, ross, bamby, laca, mstepnicki
2009-12-14 18:35:00Rhamphoryncussetmessageid: <1260815700.09.0.158850247427.issue1975@psf.upfronthosting.co.za>
2009-12-14 18:34:58Rhamphoryncuslinkissue1975 messages
2009-12-14 18:34:58Rhamphoryncuscreate