[issue25376] KeyboardInterrupt handling and traceback broken on Windows 10

Martin Panter added the comment: I am no Windows expert, but I read in Issue 18597 that Ctrl+C is treated as EOF, except that a SIGINT is also sent in the background. This would explain why you see an EOFError. The partial traceback may also be from the same EOFError. Or both cases could be tr

[issue25376] KeyboardInterrupt handling and traceback broken on Windows 10

R. David Murray added the comment: Yes, this is probably a duplicate of issue 18597. -- nosy: +r.david.murray ___ Python tracker ___ _

[issue25376] KeyboardInterrupt handling and traceback broken on Windows 10

Miikka Salminen added the comment: Did some more testing. KeyboardInterrupt traceback displays properly when pressing Ctrl+C during an infinite loop: 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"

[issue25376] KeyboardInterrupt handling and traceback broken on Windows 10

Miikka Salminen added the comment: Just tried the same in an IDLE session, but it seems to display the KeyboardInterrupt correctly: Python 3.5.0 (v3.5.0:374f501f4567, Sep 13 2015, 02:27:37) [MSC v.1900 64 bit (AMD64)] on win32 Type "copyright", "credits" or "license()" for more information. >>

[issue25376] KeyboardInterrupt handling and traceback broken on Windows 10

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 (v