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

[Vinay Sajip]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

Changes by Antoine Pitrou pit...@free.fr:


--
nosy: +Marcus.Smith, dstufft, ncoghlan, pmoore
priority: normal - critical
stage:  - needs patch
versions: +Python 3.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21699
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Nick Coghlan]

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 additional code paths exercised 
in that situation that aren't currently being adequately covered.

--
stage: needs patch - test needed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21699
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Nick Coghlan]

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 
example, at system level on *nix systems, it invokes the Python 2 version - you 
have to call pip3 to get the Python 3 version. On Windows, if the Scripts 
directory isn't on PATH, calling pip directly also doesn't work.

This bug just adds another scenario to that existing list.

(I filed https://github.com/pypa/python-packaging-user-guide/issues/107 to 
suggest also making the pip - python -m pip switch in PyPUG examples)

--
priority: critical - normal

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21699
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Justin Engel]

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'

--
components: Windows
messages: 220098
nosy: Justin.Engel
priority: normal
severity: normal
status: open
title: Windows Python 3.4.1 pyvenv doesn't work in directories with spaces.
type: crash
versions: Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21699
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[R. David Murray]

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?  (The counter argument is that paths with spaces are 
*much* more common on Windows.)

--
nosy: +r.david.murray, vinay.sajip

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21699
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[eryksun]

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 in distlib 0.1.9, which should be updated 
in the next release of pip.

https://bitbucket.org/pypa/distlib/issue/47

As a workaround, you can use `python -m pip`.

--
nosy: +eryksun

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21699
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com