Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #36949

Re: python sys.stdout and C++ iostreams::cout

References <2699150a-cf67-46ac-b863-34c92bffceaf@googlegroups.com> <mailman.592.1358437352.2939.python-list@python.org> <1908dad0-7f29-4b54-a244-7cb89510e9b0@googlegroups.com>
Date 2013-01-18 02:54 +1100
Subject Re: python sys.stdout and C++ iostreams::cout
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.594.1358438101.2939.python-list@python.org> (permalink)

Show all headers | View raw


On Fri, Jan 18, 2013 at 2:51 AM, Utpal Sarkar <doetoe@gmail.com> wrote:
> Thanks a lot Chris and Nobody! I'll have a look at dup2 for a start.

Okay. Look for code that redirects the standard I/O streams and then
exec()s another process (possibly after fork()ing); you're going to be
doing pretty much the same thing. Good luck, have fun. It's a LOT
messier than simply assigning to sys.stdout, unfortunately.

ChrisA

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


Thread

python sys.stdout and C++ iostreams::cout Utpal Sarkar <doetoe@gmail.com> - 2013-01-17 07:02 -0800
  Re: python sys.stdout and C++ iostreams::cout Nobody <nobody@nowhere.com> - 2013-01-17 15:35 +0000
  Re: python sys.stdout and C++ iostreams::cout Chris Angelico <rosuav@gmail.com> - 2013-01-18 02:42 +1100
    Re: python sys.stdout and C++ iostreams::cout Utpal Sarkar <doetoe@gmail.com> - 2013-01-17 07:51 -0800
      Re: python sys.stdout and C++ iostreams::cout Chris Angelico <rosuav@gmail.com> - 2013-01-18 02:54 +1100
    Re: python sys.stdout and C++ iostreams::cout Utpal Sarkar <doetoe@gmail.com> - 2013-01-17 07:51 -0800
  Re: python sys.stdout and C++ iostreams::cout Lie Ryan <lie.1296@gmail.com> - 2013-01-18 18:21 +1100

csiph-web