classification
Title: acknowledge signals in non-main threads
Type: Stage:
Components: Extension Modules Versions: Python 2.3
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: anthonybaxter Nosy List: anthonybaxter, langmead, loewis, mwh (4)
Priority: normal Keywords: patch

Created on 2004-12-21 05:15 by langmead, last changed 2006-12-11 04:38 by loewis.

Files
File name Uploaded Description Edit Remove
python.threadsignal.patch langmead, 2004-12-21 05:15 accept signals to threads
Messages (4)
msg47400 - (view) Author: Andrew Langmead (langmead) Date: 2004-12-21 05:15 
When a thread under Python 2.3 produces a synchronous signal 
(like a SIGSEGV) the signal is blocked and does not get handled by 
the Python interpreter. 

Python 2.4 corrected this behavior and signals sent to a thread are 
acknowledged, and then handled  the signal default behavior unless  
overridden with a signal handler. (in which case the python signal 
handler is run on the main thread.)

This is a patch for Python 2.3 for proper thread/signal behavior 
similar to  <https://sourceforge.net/tracker/?
func=detail&aid=960406&group_id=5470&atid=305470>. (This isn't 
one of the patches attached to the patch ticket, its the changes that 
mwh made in the CVS revisions listed, plus the further corrections 
in later revisions of the affected files.)
msg47401 - (view) Author: Andrew Langmead (langmead) Date: 2004-12-21 05:17 
Logged In: YES 
user_id=119306

Since mwh did the work for Python 2.4 threading, he might be the best 
person to judge this patch.
msg47402 - (view) Author: Michael Hudson (mwh) Date: 2004-12-21 14:54 
Logged In: YES 
user_id=6656

I'd be a little bit scared about applying this patch to the
2.3 branch, to be honest.  I wonder what Anthony thinks?
msg47403 - (view) Author: Martin v. Löwis (loewis) Date: 2006-12-11 04:38 
Clearly, the 2.3 branch is closed now, so I'm rejecting this patch.
History
Date User Action Args
2004-12-21 05:15:48langmeadcreate