Re: Help with pipes, buffering and pseudoterminals

From	Gregory Ewing <greg.ewing@canterbury.ac.nz>
Newsgroups	comp.lang.python
Subject	Re: Help with pipes, buffering and pseudoterminals
Date	2015-04-08 12:23 +1200
Message-ID	<cojanuFmscU1@mid.individual.net> (permalink)
References	<CAJGew6=g41cT5QXd51oaVVC5PWCnE5GWYzX5YaqDBwXb0kKUDw@mail.gmail.com> <20150407054803.GA80257@cskk.homeip.net> <mailman.85.1428403083.12925.python-list@python.org>

Show all headers | View raw

Chris Angelico wrote:
> Really? I can believe that stdout and stderr are initially duplicates,
> but stdin as well? Isn't stdin opened for reading only, and
> stdout/stderr for writing only?

It depends entirely on how the process that forked your
shell process set things up, but a quick experiment I
just did in a MacOSX terminal window suggests that it's
not really bothered about that distinction:

sh-3.2$ echo foo >&0
foo

-- 
Greg

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Help with pipes, buffering and pseudoterminals Chris Angelico <rosuav@gmail.com> - 2015-04-07 20:38 +1000
  Re: Help with pipes, buffering and pseudoterminals Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2015-04-08 12:23 +1200

csiph-web