Re: os.popen command working differently on Windows

From	Nobody <nobody@nowhere.com>
Subject	Re: os.popen command working differently on Windows
Date	2011-05-13 09:48 +0100
Message-Id	<pan.2011.05.13.08.48.23.250000@nowhere.com>
Newsgroups	comp.lang.python
References	<21581D39FA3BDF40904D75AF9653CE26064FC6D1@blrex.prog.altair.com> <mailman.1469.1305210153.9059.python-list@python.org>
Organization	Zen Internet

Show all headers | View raw

On Thu, 12 May 2011 15:21:41 +0100, Tim Golden wrote:

> os.popen returns a file-like object from which you can read any error
> messages generated.

The documentation doesn't say, but if it's anything like the Unix popen()
function, with mode='r' the returned file-like object will correspond to
the child's stdout, but error messages will normally be written to stderr.

In any case, os.popen() and similar are deprecated in favour of
subprocess.Popen().

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

Thread

Re: os.popen command working differently on Windows Tim Golden <mail@timgolden.me.uk> - 2011-05-12 15:21 +0100
  Re: os.popen command working differently on Windows Nobody <nobody@nowhere.com> - 2011-05-13 09:48 +0100
  Re: os.popen command working differently on Windows Hans Mulder <hansmu@xs4all.nl> - 2011-05-13 19:10 +0200

csiph-web