[issue20894] COMSPEC with multiple paths breaks subprocess.call

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 ___

[issue20894] COMSPEC with multiple paths breaks subprocess.call

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: http://superuser.com/questions/446595/is-it-valid-for-com

[issue20894] COMSPEC with multiple paths breaks subprocess.call

Changes by Yury Selivanov : -- nosy: +brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue20894] COMSPEC with multiple paths breaks subprocess.call

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'] (http://stackoverflow.com/question