[issue21699] Windows Python 3.4.1 pyvenv doesn't work in directories with spaces.

Vinay Sajip added the comment: I'll close this as it doesn't seem to be a Python bug. -- resolution: -> not a bug stage: test needed -> resolved status: open -> closed ___ Python tracker __

[issue21699] Windows Python 3.4.1 pyvenv doesn't work in directories with spaces.

Nick Coghlan added the comment: Also reducing the priority back to "normal" - the docs at https://docs.python.org/3/installing/ already specifically recommend the "python -m pip" spelling because it's the most universal. Calling "pip" directly is known to fail in a variety of situations. For

[issue21699] Windows Python 3.4.1 pyvenv doesn't work in directories with spaces.

Nick Coghlan added the comment: Note that this is also tricky to test - we *don't* currently activate the venv in the test suite, instead relying on a "-m" invocation. However, I think this error shows that a new automated test is needed that covers the activation case, as there are some addit

[issue21699] Windows Python 3.4.1 pyvenv doesn't work in directories with spaces.

Changes by Antoine Pitrou : -- nosy: +Marcus.Smith, dstufft, ncoghlan, pmoore priority: normal -> critical stage: -> needs patch versions: +Python 3.5 ___ Python tracker ___ ___

[issue21699] Windows Python 3.4.1 pyvenv doesn't work in directories with spaces.

eryksun added the comment: The py.exe launcher relies on manual quoting in the shebang line. That's the case for the shebang embedded in this pip executable. The problem is the "simple launcher" used by distlib 0.1.8. It always quotes the executable, even if it's already quoted. This is fixed

[issue21699] Windows Python 3.4.1 pyvenv doesn't work in directories with spaces.

R. David Murray added the comment: This *can't* work on Linux (see issue 20622). I don't know if it is possible to make it work on Windows, but I wonder: even if it is should we do so, since the point of the launcher is to make shebang lines work on Windows more or less how they do on Unix?

[issue21699] Windows Python 3.4.1 pyvenv doesn't work in directories with spaces.

New submission from Justin Engel: Venv virtual environments don't work with spaces in the path. (env) C:\My Directory\path > pip -V Fatal error in launcher: Unable to create process using '""C:\My Directory\path\env\Scripts\python.exe"" "C:\My Directory\path\env\Scripts\pip.exe" -V' -