Eryk Sun added the comment:
> Even is IDLE is started from a console, the user execution process
> is not attached to one.
Actually, the execution process is attached to a console, but it doesn't use it
for sys.std*. Try
open('con', 'w').write('spam\n')
> It is much like closing a terminal Window with [X], and restarting
> the terminal and python, instead of using ^C.
There's no default handler for SIGBREAK, so when working in the console it's
typically better to use Ctrl+Break to kill Python. This preserves the console's
arrow-key & F7 input history and scrollback buffer.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29926>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
