[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

Change by Eryk Sun : -- components: +Interpreter Core -Library (Lib) versions: +Python 3.10 -Python 3.7 ___ Python tracker ___ ___

[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

Change by Eryk Sun : -- Removed message: https://bugs.python.org/msg359933 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

Eryk Sun added the comment: On second thought, I think the fact that the console leaves the previously entered text on the line is ugly and confusing. The text isn't in the input buffer, so it won't be read. Yet there's no way for the user to even clear it -- not by escape or backspace. I

[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

Change by Zackery Spytz : -- nosy: +ZackerySpytz versions: +Python 3.8, Python 3.9 -Python 3.6 ___ Python tracker ___ ___

[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

Change by Zackery Spytz : -- pull_requests: +17383 pull_request: https://github.com/python/cpython/pull/17976 ___ Python tracker ___

[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

Eryk Sun added the comment: > 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

[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

Valeriya Sinevich added the comment: I posted a PR but the problem with it is that all the input before the ignored Ctrl+C is lost. -- nosy: +valer ___ Python tracker ___

[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

Change by Valeriya Sinevich : -- keywords: +patch pull_requests: +7878 stage: test needed -> patch review ___ Python tracker ___

[issue28166] WindowsConsoleIO misbehavior when Ctrl+C is ignored

New submission from Eryk Sun: _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 >>>