Thanks for response,
Cant reproduce it locally, so maybe there is some issue with urwid and SIGINT usage, or other sporadic issue. Anyway such error was possible only because of incorrect exception handler, and this will be fixed in 5.0.
Thanks for response,
Cant reproduce it locally, so maybe there is some issue with urwid and SIGINT usage, or other sporadic issue.
Anyway such error was possible only because of incorrect exception handler, and this will be fixed in 5.0.