[Python-bugs-list] [ python-Bugs-439992 ] [win32] KeyboardInterrupt Not Caught
noreply@sourceforge.net
noreply@sourceforge.net
Tue, 11 Dec 2001 21:34:23 -0800
Bugs item #439992, was opened at 2001-07-10 02:24
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=439992&group_id=5470
Category: Python Interpreter Core
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Tim Peters (tim_one)
Summary: [win32] KeyboardInterrupt Not Caught
Initial Comment:
The following program, run under unix (FreeBSD 4.3) and Windows 2000 SP2
with the command line: python test.py
In both cases, running python 2.1.
The program works as expected under unix and IDLE on Windows 2000, but it
does *not* catch the interrupt in the command line version of Win32 python...
i.e., The traceback message appears rather than my "Leaving Dodge..." message.
while 1:
try:
x = raw_input().upper()
print x
except KeyboardInterrupt:
print "Leaving Dodge...\n"
break
----------------------------------------------------------------------
>Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-11 21:34
Message:
Logged In: YES
user_id=6380
Shall we close this as Won't Fix? Is there a point in
keeping it open while we know we can't fix it?
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2001-08-07 08:51
Message:
Logged In: YES
user_id=31435
For posterity, a delightfully confused section of
MS's "signal" docs:
"""
Note SIGINT is not supported for any Win32 application
including Windows NT and Windows 95. When a CTRL+C
interrupt occurs, Win32 operating systems generate a new
thread to specifically handle that interrupt. This can
cause a single-thread application such as UNIX, to become
multithreaded, resulting in unexpected behavior.
"""
I kid you not.
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2001-08-07 06:59
Message:
Logged In: YES
user_id=6380
Yes, I'm afraid signal handling doesn't always work on
Windows.
I don't know Windows enough to understand how to fix this.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=439992&group_id=5470