Message198188
| Author |
techtonik |
| Recipients |
docs@python, techtonik |
| Date |
2013年09月21日.07:29:54 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1379748595.57.0.00736365306091.issue19060@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I always thought that subprocess is replacing all other methods of executing external programs from Python and it is a preferred way. Perhaps I was not attentive that people isolate:
os.system
os.spawn*
os.popen*
and
os.exec*
While subprocess replaces three first, it doesn't do this with the last one. The documentation should mention this in the header block. Proposed edit:
...
replace several other, older modules and functions, such as:
os.system
os.spawn*
os.popen*
popen2.*
commands.*
+ Note that it doesn't replace other ways of executing external
+ processes from Python, such as:
+
+ os.exec*
Information about how the subprocess module can be used
... |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年09月21日 07:29:55 | techtonik | set | recipients:
+ techtonik, docs@python |
| 2013年09月21日 07:29:55 | techtonik | set | messageid: <1379748595.57.0.00736365306091.issue19060@psf.upfronthosting.co.za> |
| 2013年09月21日 07:29:55 | techtonik | link | issue19060 messages |
| 2013年09月21日 07:29:54 | techtonik | create |
|