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 cvrebert
Recipients cvrebert, docs@python
Date 2010-07-26.05:24:05
SpamBayes Score 1.7832093e-07
Marked as misclassified No
Message-id <1280121849.18.0.464291520909.issue9382@psf.upfronthosting.co.za>
In-reply-to
Content
http://docs.python.org/py3k/library/os.html  currently mentions os.popen() in several places. The docs for os.popen() itself say:
'These functions are described in section "File Object Creation"'

However, unlike the 2.x version of that section ( http://docs.python.org/library/os.html#file-object-creation ), the os.popen*() family is not documented there [or indeed anywhere] anymore ( http://docs.python.org/py3k/library/os.html#os-newstreams ); the entire section now only documents os.fdopen().

The 2.7 docs say that the os.popen*() family are deprecated, and indeed, of the family, only os.popen() seems to still exist in Python 3.x (at least based on my testing via ideone.com).

Thus, from what I can see, one of the following is the case:
(A) The entire os.popen*() family is supposed be gone in Python 3.x, so os.popen() should be removed entirely from both the code and the docs.
(B) os.popen() is the sole legitimate survivor of its family, and should be properly documented again.
(C) os.popen() was left in as a kludge, shouldn't be mentioned in the docs, and possibly should be renamed os._popen() to reflect its status.

So, which one of these is it?
History
Date User Action Args
2010-07-26 05:24:09cvrebertsetrecipients: + cvrebert, docs@python
2010-07-26 05:24:09cvrebertsetmessageid: <1280121849.18.0.464291520909.issue9382@psf.upfronthosting.co.za>
2010-07-26 05:24:07cvrebertlinkissue9382 messages
2010-07-26 05:24:05cvrebertcreate