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 ncoghlan
Recipients docs@python, ncoghlan
Date 2011-10-21.05:25:00
SpamBayes Score 7.425031e-07
Marked as misclassified No
Message-id <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
In-reply-to
Content
Many typical subprocess use cases can now be handled simply via the convenience functions:

  subprocess.call()
  subprocess.check_call()
  subprocess.check_output()

However, readers of the documentation could be forgiven for not realising that, since the docs dive right in with Popen() and will scare most readers away in search of more user friendly APIs (or even other languages).

The module documentation should be reordered to introduce the helper function first, then Popen afterwards.

The "subprocess replacements" [1] section would ideally help address this, but it hasn't been updated to use the convenience function, instead using confusing direct calls to Popen.

[1] http://docs.python.org/library/subprocess.html#subprocess-replacements
History
Date User Action Args
2011-10-21 05:25:02ncoghlansetrecipients: + ncoghlan, docs@python
2011-10-21 05:25:02ncoghlansetmessageid: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
2011-10-21 05:25:01ncoghlanlinkissue13237 messages
2011-10-21 05:25:00ncoghlancreate