_PyOS_WindowsConsoleReadline should continue to read when interrupted by Ctrl+C if SIGINT is ignored or the handler doesn't raise an exception. Currently it breaks out of the read loop, which looks like an EOF: >>> import signal >>> signal.signal(signal.SIGINT, signal.SIG_IGN) <built-in function default_int_handler> >>> input() Traceback (most recent call last): File "", line 1, in EOFError Also, in this case Ctrl+C quits the REPL. Similarly sys.stdin.buffer.raw should retry a read. Instead a read(1) returns an empty string and readall() raises an exception: >>> sys.stdin.buffer.raw.read(1) b'' >>> sys.stdin.buffer.raw.read() Traceback (most recent call last): File "", line 1, in OSError: [WinError 87] The parameter is incorrect
> all the input before the ignored Ctrl+C is lost The console host process doesn't know that Python is ignoring Ctrl+C, so it cancels the read and flushes the input buffer. For now, we have to accept this as a limitation of relying on the high-level console API (i.e. ReadConsoleW with the default settings), which implements command-line editing, aliases and history completely in the console host process. Restarting the read with a flushed input buffer is better than raising EOFError or exiting the REPL. In the future, Python's console readline implementation could hook deeper into the operation by temporarily disabling the console's ENABLE_PROCESSED_INPUT mode and using the pInputControl parameter to handle ^C and ^H (backspace). This would be fairly involved but still an imperfect solution because ^C will replace whichever character is under the cursor (fine if the cursor is at the end of the line, but otherwise pretty clunky). The only way to have complete control is to use the low-level ReadConsoleInput function. pyreadline implements this via ctypes.
