This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients cvrebert, docs@python, r.david.murray
Date 2010-07-26.11:31:33
SpamBayes Score 0.004220073
Marked as misclassified No
Message-id <1280143895.17.0.691069247007.issue9382@psf.upfronthosting.co.za>
In-reply-to
Content
(D) in python 3, os.popen has been reimplemented using subprocess.Popen.
So the other mentions of os.popen should probably be replaced with mentions of subprocess.Popen.

Your (C) is close...the continued existence of os.popen in Python3 is, I think, a bit of a kludge (I wasn't around for the discussion), but a backward compatibility one.  I don't know if there is a plan to deprecate it, but I suspect not.  On the other hand I certainly wouldn't recommend using it, since it does an import inside the function, which can get one into trouble if one uses threads.
History
Date User Action Args
2010-07-26 11:31:35r.david.murraysetrecipients: + r.david.murray, cvrebert, docs@python
2010-07-26 11:31:35r.david.murraysetmessageid: <1280143895.17.0.691069247007.issue9382@psf.upfronthosting.co.za>
2010-07-26 11:31:33r.david.murraylinkissue9382 messages
2010-07-26 11:31:33r.david.murraycreate