Joshua Ellinger added the comment:
The safest fix would be to make subprocess strip double-quotes from the
executable path.
Double quote (") is not an allowed character in Windows file systems. There is
no case under
which it can be correct to spawn a process in Windows where the pa
Joshua Ellinger added the comment:
Having pip not work after a straight install to the normal place you'd install
it on windows can't be a feature.
Even after I changed the .exe, pip itself breaks on the same problem.
Basically, you can't install python to
the normal place o
New submission from Joshua Ellinger:
The problem is that the python path name is quoted if it contains spaces. The
launcher does not remove the extra quotes and fails.
I 'solved' by editing the pip.exe to remove the quotes.
ps - Windows programs are normally installed under c:\Pro
