Windows: subprocess won't run different Python interpreter

[Thorsten Kampe]

* eryk sun (Fri, 11 Nov 2016 06:23:50 +0000)
> 
> That's the application directory, which is the first place
> CreateProcess looks (via the SearchPath call), as both of my examples
> shows. In my case python.exe is located in the standard 3.5 system
> installation path, "C:\Program Files\Python35".

Okay, it looks like I read your first answer not thorough enough.

So if the application's directory is always searched then the issue 
should be reproducible with any native (non-Cygwin) Windows 
interpreter:

"""
tcc> \PortableApps\TCC_RT\tcc.exe /c run-TEST.btm
unset PATH
tcc.exe /c ver
TCC: C:\Documents\batch\run-TEST.btm [2]  Unbekannter Befehl 
"tcc.exe"
"""

So TCC can't find itself with an empty PATH. That's how Python 
(subprocess) should also work.

Thorsten