Michiel de Hoon added the comment:
As it happens, we just ran into the same bug.
To reproduce this issue, run
from Tkinter import *
Tk()
Then Ctrl-C will not generate a KeyboardInterrupt.
At first glance, the solution suggested by the original poster seems good. Can
this issue by reopened?
Michiel de Hoon added the comment:
I have opened a new issue 23237 for this bug; please see
http://bugs.python.org/issue23237
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3180
___
STINNER Victor added the comment:
This issue is now closed. Please open a new issue. You should mention
your OS and the Python version at least.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3180
STINNER Victor added the comment:
I don't understand how to reproduce the issue, there is no unit test nor a
description how to reproduce the issue.
I'm not aware of a bug where CTRL+c is simply ignored. CTRL+c is now well
handled in Python 2.7, on Linux and Windows at least.
Since the bug
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: -BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3180
___
___
Mark Lawrence breamore...@yahoo.co.uk added the comment:
I'm unsure as to whether this is a feature request or a behaviour problem,
anyone? Regardless could a core dev take a look at the patch which involves
changes to the API for PyOS_InputHook, see msg68638.
--
nosy: +BreamoreBoy
Daniel Diniz aja...@gmail.com added the comment:
Michael,
How does this interact with the fix from issue 706406?
--
components: +Extension Modules -None
nosy: +ajaksu2
priority: - normal
stage: - test needed
versions: +Python 2.7, Python 3.2 -Python 2.6
New submission from Michael Abbott [EMAIL PROTECTED]:
The (undocumented!) API for PyOS_InputHook has two defects which are
addressed in the attached patch (at least when using the readline
module): firstly the called hook currently has to guess that input will
come on descriptor 0; secondly, any
