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. ---------- nosy: +vadmium resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> On Windows sys.stdin.readline() doesn't handle Ctrl-C properly _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14287> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
