[issue42020] interpreter hangs forever on invalid input

denis added the comment: I do confirm that different terminals react differently (xterm doesn't hang) Definitely not a python bug -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue42020] interpreter hangs forever on invalid input

STINNER Victor added the comment: I don't see anything wrong with Python itself and I suggest to close the issue as "not a bug". -- ___ Python tracker ___

[issue42020] interpreter hangs forever on invalid input

Eryk Sun added the comment: In Windows 10 2004, CSI is currently supported by the console host (conhost.exe) if virtual-terminal mode is enabled. Windows Terminal Preview supports many more C1 control codes, as will conhost.exe in the next release of Windows 10. This should be 'fun'

[issue42020] interpreter hangs forever on invalid input

Eryk Sun added the comment: The terminal you're using apparently implements C1 controls [1]. U+009B is the Control Sequence Introducer (CSI) for ANSI escape sequences. U+0090 starts a Device Control String (DCS), and it gets terminated by U+009C, a String Terminator (ST). For example, in

[issue42020] interpreter hangs forever on invalid input

New submission from denis : Python 3.8.5, Python 3.7.3 When trying to print invalid unicode, interpreter goes to a completely unresponsive state >>> print("\x9b") eyboardInterrupt >>> print("\xa5") ¥ >>> print("\x95") >>> print("\x90") denis@debian:~$ -- components: Unicode