Message161385
| Author |
r.david.murray |
| Recipients |
cvrebert, docs@python, r.david.murray, techtonik |
| Date |
2012年05月22日.22:24:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1337725474.4.0.425778552951.issue14879@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I don't think that those additions make anything clearer, I'm afraid.
"child python process" would seem to imply raised in the new python running in the child process, which is clearly not true.
Hmm. I seem to remember having this discussion before. The current statement is in fact exactly correct. When shell=True the new program being run is 'sh' (or similar). So the error message is coming from the program being run successfully by subprocess. End of story.
So, we could add a clarfication: "If shell=True, the 'new program' being run is the shell, which may generate its own errors based on the shell command passed to it (such as command not found). These will not result in exceptions." |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年05月22日 22:24:34 | r.david.murray | set | recipients:
+ r.david.murray, techtonik, cvrebert, docs@python |
| 2012年05月22日 22:24:34 | r.david.murray | set | messageid: <1337725474.4.0.425778552951.issue14879@psf.upfronthosting.co.za> |
| 2012年05月22日 22:24:33 | r.david.murray | link | issue14879 messages |
| 2012年05月22日 22:24:33 | r.david.murray | create |
|