5 messages in org.python.python-bugs-list[ python-Bugs-875692 ] Ctrl-C doesn't...
FromSent OnAttachments
SourceForge.netMar 27, 2004 6:56 am 
SourceForge.netMar 27, 2004 11:00 am 
SourceForge.netMar 27, 2004 2:04 pm 
SourceForge.netMar 28, 2004 2:10 am 
SourceForge.netMar 28, 2004 5:00 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[ python-Bugs-875692 ] Ctrl-C doesn't work with sleepy main threadActions...
From:SourceForge.net (nore@sourceforge.net)
Date:Mar 27, 2004 6:56:20 am
List:org.python.python-bugs-list

Bugs item #875692, was opened at 2004-01-12 21:37 Message generated for change (Comment added) made by rhamphoryncus You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=875692&group_id=5470

Category: Threads Group: Python 2.3 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: Ctrl-C doesn't work with sleepy main thread

Initial Comment: [forwarded from http://bugs.debian.org/226547]

I only have access to Debian systems ... Maybe this is related to 846817?

I'm trying to do some basic threading with Python. However, there are times when Ctrl-C fails to cause a KeyboardInterrupt in the main thread.

Here is a test program that illustrates the problem. As written, I cannot interrupt it with Ctrl-C (nothing happens even if I hold it down). If I uncomment the print statement in the main thread, then I can interrupt it with Ctrl-C.

It seems like adding the print in the main thread gives the main thread a "chance to run" where it finally notices the signal from the Ctrl-C. However, I shouldn't have to use hacks like this to get this to work.

People on comp.lang.python could not reproduce this on Fedora and some others, so I'm posting it here (maybe some problem with Debian's libc6?).

----------------------------------------------------------------------

Comment By: Adam Olsen (rhamphoryncus) Date: 2004-03-27 11:56

Message: Logged In: YES user_id=12364

I use debian and can reproduce it. Python package version 2.3.3-6. I also tried with python 2.2 and the bug was NOT present. Package version 2.2.3-9.

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh) Date: 2004-01-13 11:16

Message: Logged In: YES user_id=6656

As the guy says in the bug report, the comp.lang.python opinion was that this was a problem in debian! Can someone with a debian machine (or any other -- I can't) reproduce this?

----------------------------------------------------------------------