Message 248029 - Python tracker

➜

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	paul.moore
Recipients	paul.moore, phbarnacle, steve.dower, tim.golden, zach.ware
Date	2015-08-05.10:51:55
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1438771921.13.0.916314416605.issue24793@psf.upfronthosting.co.za>
In-reply-to

Content
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 to the executable - "subprocess.call(["C:\\Python34\\python.exe"])".

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  to the executable - "subprocess.call(["C:\\Python34\\python.exe"])".

History
Date	User	Action	Args
2015-08-05 10:52:03	paul.moore	set	recipients: + paul.moore, tim.golden, zach.ware, steve.dower, phbarnacle
2015-08-05 10:52:01	paul.moore	set	messageid: <1438771921.13.0.916314416605.issue24793@psf.upfronthosting.co.za>
2015-08-05 10:52:00	paul.moore	link	issue24793 messages
2015-08-05 10:51:56	paul.moore	create