[issue14287] sys.stdin.readline and KeyboardInterrupt on windows

Martin Panter added the comment: If the interrupt truly occurred after readline() succeeded, then x should contain actual input from the user, not the empty string. So I think this is a valid bug. However it looks like this is the same as Issue 18597, which has more discussion. -- no

[issue14287] sys.stdin.readline and KeyboardInterrupt on windows

Mark Lawrence added the comment: FWIW the same occurs on Windows 7 with 3.5.0 but given there are known differences between Windows and *nix is this really an issue? -- nosy: +BreamoreBoy ___ Python tracker __

[issue14287] sys.stdin.readline and KeyboardInterrupt on windows

New submission from Musashi Tamura : I run z.py and press Ctrl-C. '' Traceback (most recent call last): File "z.py", line 7, in print(repr(x)) KeyboardInterrupt I think '' should not be printed. This sometimes occurs on Python 3.2.2 and 2.7.2 AMD64 on Windows7, but doesn't occur on ubu