[docs] [issue34115] code.InteractiveConsole.interact() closes stdin
report at bugs.python.org
Tue Jul 24 15:43:22 EDT 2018
Yonatan Zunger <zunger at humu.com> added the comment:
Eryk: Thanks for finding that! So that I'm sure I understand, if 34187 is
resolved, does that mean the stdin.close() is no longer required at all in
On Sun, Jul 22, 2018 at 2:12 AM Eryk Sun <report at bugs.python.org> wrote:
> Eryk Sun <eryksun at gmail.com> added the comment:
> > On Windows Console, sys.stdin.close() does not prevent a second
> > interact call. This might be considered a bug.
> This is a bug in io._WindowsConsoleIO.
> In Python 3, the sys.std* file objects that get created at startup use
> >>> sys.stdin.buffer.raw.closefd
> >>> sys.stdout.buffer.raw.closefd
> >>> sys.stderr.buffer.raw.closefd
> Since the REPL uses C FILE streams (or in 3.6+ the underlying console file
> handle in Windows), closing sys.stdin does not cause the REPL to exit, and
> the PyOS_ReadLine call in the interactive loop continues to work in both
> POSIX and Windows.
> That said, closing sys.stdin should cause input() to raise ValueError due
> to sys.stdin.fileno() failing (i.e. take the non-tty path) and subsequently
> sys.stdin.readline() failing. A second call to
> code.InteractiveConsole.interact() should thus fail. The issue is that the
> fileno() method of _WindowsConsoleIO isn't raising ValueError like it
> should when the file is closed and closefd is false. I've created issue
> 34187 with a suggested fix.
> nosy: +eryksun
> Python tracker <report at bugs.python.org>
Python tracker <report at bugs.python.org>
More information about the docs