Message177694
| Author |
pepalogik |
| Recipients |
asvetlov, chris.jerdonek, cvrebert, docs@python, ned.deily, pepalogik, python-dev |
| Date |
2012年12月18日.16:16:16 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1355847379.74.0.595505492306.issue15533@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Hi,
I am using Python 3.2.3 on Windows XP. I encountered a problem with subprocess.call when using the cwd parameter. I used Google to look for a solution and I found this issue in Python tracker. But this issue seems absolutely reversed!
The subprocess documentation says this: "In particular, the function looks for executable (or for the first item in args) relative to cwd if the executable path is a relative path." But this is NOT true. If I use the path relative to cwd, I get Windows Error 2 (system cannot find the file). If I change the executable's path to be relative to the current directory, where the script is running (i.e. NOT the cwd parameter passed to subprocess.call), it works fine. |
|