Martin Panter added the comment:

I don’t think SIGQUIT handling is a big problem. But even with the new change, 
it is still easy to screw up the terminal in many cases, so I wouldn’t say this 
is fixed yet. Steps for Python 3 in a small 80 × 25 terminal on Linux:

* import _pyio; help(_pyio)
* Hit Ctrl-C

Steps for Python 2:

* import _pyio; help(_pyio)
* Hit Ctrl-C
* Hit Space ten times to scroll down. Alternatively, hit Ctrl-C a second time.

I am posting a quick patch which I think should fix this in Python 3 by 
deferring the traceback until after the child has finished. Another method is 
using the signal module like 
<https://github.com/vadmium/pacman-tools/blob/9ffdd88/roopwn#L976>, but that’s 
probably too platform-specific for the pydoc module.

----------
Added file: http://bugs.python.org/file38730/interrupt.patch

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue23792>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to