[issue1975] signals in thread problem

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1975] signals in thread problem

Guido van Rossum added the comment: Well okay than I can confirm that OSX is *not* affected by this OS bugginess. -- keywords: +patch __ Tracker <[EMAIL PROTECTED]> __

[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 class MyThread(Thre

[issue1975] signals in thread problem

Guido van Rossum added the comment: Actually I see the same behavior under Linux and OSX: the first ^C interrupts the select() call, after that ^C is ignored. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> _

[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 problem