New submission from Miikka Salminen:
Pressing Ctrl+C to raise a KeyboardInterrupt while waiting for user input in an
input() call yields an incomplete traceback.
The behaviour appears in a Python REPL session started by issuing "python"
without quotes in a Windows cmd session:
Python 3.5.0 (v3.5.0:374f501f4567, Sep 13 2015, 02:27:37) [MSC v.1900 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> input("Question: ")
Question: Traceback (most recent call last):
File "<stdin>", line 1, in <module>
>>>
When executing input_test.py (a single line Python source code file containing
just an input("Question: ") call) from the cmd prompt by issuing "python
input_test.py" without quotes, every other time the traceback is incomplete and
every other time the Ctrl+C keypress yields, erroneously, an EOFError instead
of a KeyboardInterrupt:
C:\x>python input_test.py
Question: Traceback (most recent call last):
File "input_test.py", line 1, in <module>
input("Question: ")
EOFError
^C
C:\x>python input_test.py
Question: Traceback (most recent call last):
File "input_test.py", line 1, in <module>
C:\x>
----------
components: Interpreter Core, Windows
messages: 252800
nosy: mdf, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: KeyboardInterrupt handling and traceback broken on Windows 10
type: behavior
versions: Python 3.4, Python 3.5
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25376>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
