homepage

At least on Windows, input() doesn't raise KeyboardInterrupt when Ctrl-C is hit in Python 3.3 (it does in Python 3.2).
3.3:
>>> x = input() # Ctrl-C hit - no exception raised
>>> x
NameError
3.2:
>>> x = input() # Ctrl-C hit
KeyboardInterrupt

Seems to be windows specific. It works fine on Linux and Solaris.

It may be related to the following commit:
changeset: 77861:9523c122d6fc
user: Tim Golden <mail@timgolden.me.uk>
date: Fri Jun 29 18:39:26 2012 +0100
files: Parser/myreadline.c
description:
Issue #1677: Handle better a race condition between the interactive interpreter and
the Ctrl-C signal handler on Windows

@Drekin: What is your Windows version? How did you start Python?

I have Windows Vista Business SP2, 64-bit, (6.0.6002). If I start Python any way (from console, from shortcut, via py.exe or not) the same behavior occurs.

However it raises the exception correctly in IDLE.
The same behavior occured on Windows 7 Home Premium SP1, 64-bit, (6.1.7601).

That's because IDLE uses a completely different input loop from the
console interpreter.
I'll try to get to this but I'm chock-a-block with other work at the
moment. If anyone else wants to dig, please do so. if the worst came to
the worst we could back out my previous changeset but that would still
leave us with an intermittent race-condition.

There is related weird behavior:
>>> try:
... input()
... except KeyboardInterrupt:
... print("exception occured")
...
# Ctrl-C hit
Traceback (most recent call last):
 File "<stdin>", line 2, in <module>
KeyboardInterrupt
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
 File "<stdin>", line 2, in <module>
KeyboardInterrupt
>>>
Seems like handling of Ctrl-C is kind of "out of sync".

Maybe this is related to
 http://bugs.python.org/issue13673
which causes PyTraceback_Print() to fail if a signal is received but PyErr_CheckSignals() has not been called.
Note that wrapping in "try: ... except: raise" makes a traceback appear:
>>> try: input()
... except: raise
...
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
KeyboardInterrupt
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
KeyboardInterrupt

Adding PyErr_CheckSignals() after PyOS_Readline() in builtin_input() seems to fix the problem.

+1
Richard - are you in a position to commit / push?

New changeset 241cd716bf5f by Richard Oudkerk in branch '3.3':
Issue #17619: Make input() check for Ctrl-C correctly on Windows.
http://hg.python.org/cpython/rev/241cd716bf5f 

> Richard - are you in a position to commit / push?
Done.