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 krawyoti
Recipients georg.brandl, krawyoti
Date 2009-07-15.08:35:36
SpamBayes Score 7.5374875e-05
Marked as misclassified No
Message-id <1247646939.28.0.091306950041.issue6490@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation in Python 2.6 claims os.popen is deprecated [1]. This
is probably a false claim. I think that at some point os.popen got
confused with os.popen2, os.popen3, os.popen4 and the popen2 module, all
of which are correctly deprecated.

I bring three forward three pieces of evidence that os.popen is *not*
deprecated:

i) In Python 3.1, unlike the others, os.popen is still present and is
not even deprecated. [2]

ii) Unlike the others, using os.popen does not raise a DeprecationWarning;

iii) Unlike the others, its implementation is lifted straight from the
posix module.

--
[1] http://docs.python.org/2.6/library/os.html#os.popen
[2] http://docs.python.org/3.1/library/os.html#os.plock
History
Date User Action Args
2009-07-15 08:35:40krawyotisetrecipients: + krawyoti, georg.brandl
2009-07-15 08:35:39krawyotisetmessageid: <1247646939.28.0.091306950041.issue6490@psf.upfronthosting.co.za>
2009-07-15 08:35:38krawyotilinkissue6490 messages
2009-07-15 08:35:36krawyoticreate