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 pitrou
Recipients Rhamphoryncus, bamby, exarkun, georg.brandl, gvanrossum, laca, movement, mstepnicki, pitrou, ross
Date 2009-12-15.10:54:21
SpamBayes Score 7.043418e-07
Marked as misclassified No
Message-id <>
Well, the history on this looks a bit complicated and I don't really
know the details, but witness the first sentences of the initial message
in issue960406:

“This is a patch which will correct the issues some people 
have with python's handling of signal handling in threads. It 
allows any thread to initially catch the signal mark it as 
triggered, allowing the main thread to later process it. (This 
is actually just restoring access to the functionality that was 
in Python 2.1)”

Apparently Python has been hesitating between both behaviours.

> The Python documentation clearly states that 
> there is no user accessible Python functions that can modify
> per-thread signal mask, so it is currently impossible to solve the
> problem with just Python code.

Well as I already said we could introduce this missing feature. Ideas
and patches welcome.
Date User Action Args
2009-12-15 10:54:25pitrousetrecipients: + pitrou, gvanrossum, georg.brandl, exarkun, Rhamphoryncus, movement, ross, bamby, laca, mstepnicki
2009-12-15 10:54:24pitrousetmessageid: <>
2009-12-15 10:54:22pitroulinkissue1975 messages
2009-12-15 10:54:21pitroucreate