[issue1975] signals not always delivered to main thread, since other threads have the signal unmasked

Andriy Pylypenko added the comment: > Well as I already said we could introduce this missing feature. Ideas > and patches welcome. Well, this would be definitely a working solution. -- ___ Python tracker <http://bugs.python.org/

[issue1975] signals not always delivered to main thread, since other threads have the signal unmasked

Andriy Pylypenko added the comment: Let me add my 2 cents. I understood the considerations about differences between Python code level interrupt handling and OS level interrupts. What I cannot get is why to preserve the handling of signals in the user threads on OSes like FreeBSD and

[issue1975] signals in thread problem

Andriy Pylypenko added the comment: I'm sorry I've forgotten to add one important thing to the script - the t.setDaemon(True) call, as without it the main thread will wait for the user thread to stop explicitly. So the correct script is: some_time = 600 # seconds clas

[issue1975] signals in thread problem

New submission from Andriy Pylypenko: Hello, This issue is actually a follow up of issue 960406. The patch applied there brought in a problem at least under FreeBSD. The problem is extremely annoying so I made an effort to uncover the source of it. Here is an example code that shows the