[issue20894] COMSPEC with multiple paths breaks subprocess.call

2014-03-12 Thread Elja van Tol
New submission from Elja van Tol: I tried a simple console command: import subprocess subprocess.call([dir], shell=True) Which failed with an WindowsError 2, (could not find file) After much googling i found out that this is caused by os.environ['COMSPEC']

[issue20894] COMSPEC with multiple paths breaks subprocess.call

2014-03-12 Thread Yury Selivanov
Changes by Yury Selivanov yselivanov...@gmail.com: -- nosy: +brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20894 ___ ___

[issue20894] COMSPEC with multiple paths breaks subprocess.call

2014-03-12 Thread R. David Murray
R. David Murray added the comment: This was a misconfiguration of your system. It is not a bug in Python. (Unless can find a microsoft reference that says that COMPSPEC can contain more than one path? I don't think you will; see, eg:

[issue20894] COMSPEC with multiple paths breaks subprocess.call

2014-03-12 Thread Elja van Tol
Elja van Tol added the comment: I stand corrected, now i have to find out why my comspec was filled with nonsense. Sorry for the trouble! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20894