Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!feeds.phibee-telecom.net!dedekind.zen.co.uk!zen.net.uk!hamilton.zen.co.uk!reader02.news.zen.co.uk.POSTED!not-for-mail From: Nobody Subject: Re: os.popen command working differently on Windows Date: Fri, 13 May 2011 09:48:52 +0100 User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Message-Id: Newsgroups: comp.lang.python References: <21581D39FA3BDF40904D75AF9653CE26064FC6D1@blrex.prog.altair.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Lines: 12 Organization: Zen Internet NNTP-Posting-Host: 9b973805.news.zen.co.uk X-Trace: DXC=l;bBchdJI[@L2Ih^^87?RGYjZGX^207PK` 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().