eryksun added the comment:
Popen calls Windows [CreateProcess][1]. If the Popen "executable" argument
isn't used or if the file from the command line doesn't include a directory
path, then CreateProcess searches for it in the following directories:
1. The directory from which the applicati
Paul Moore added the comment:
This is standard Windows behaviour. Executables are always located first in the
directory where your program (in this case the Python executable) is running
from - even before searching PATH.
If you want to use a different Python, you should specify the full path
New submission from Gregor:
I just noticed that there is a litte inconvenience when I try to invoke
'python' via subprocess.call passing an environment (%PATH%) from a script. I
pass an environment where %PATH% only contains one directory where a
python2.7.3-exe is present (I checked with
"su
