#114 WinPython PREFIX wrong if conflicting python interpreter already on PATH
First of all, thank you for this excellent product. Having a portable version of Python for Windows where there are not readily available compilers is huge!
So I am posting this warning, because I could not find it elsewhere, maybe wrong search terms?
If there is another Python interpreter on the system (or user) path, then unless in your current shell, PYTHONHOME=<\path\to\winpython> is set, then:
IPython does not work
site-packages is not found
And regardless, unless the user can remove the competing Python interpreter from the path, then WinPython-Control-Panel, Spyder, IPython-QtConsole fail.
In my case, there was a CollabNet Subversion server that included a Python interpreter that was on the path, so it was not immediately obvious to me that Python was already installed.
I think this can be fixed in future versions by setting PYTHONHOME explicitly in the command shell and in any shells that are used to compile standalone apps like the control panel, IPython-QtConsole or Spyder.
Hi!
Since WinPython is portable,it shouldn't be necessary to remove a competing interpreter because you shouldn't need modify PYTHONHOME or the system path.