Cannot create a virtualenv with a trailing space in the name

[jessamynsmith]

First off, I think that creating directories with leading or trailing spaces in the name is a terrible thing to do, but it is legal in most operating systems. In Mac OSX I am able to create a virtualenv named " space ", but on linux it fails as follows:

$ virtualenv "trailing space "
New python executable in trailing space /bin/python
ERROR: The executable trailing space /bin/python is not functioning
ERROR: It thinks sys.prefix is u'/home/vagrant/trailing space' (should be u'/home/vagrant/trailing space ')
ERROR: virtualenv is not compatible with this system or executable

I only discovered this because I was writing tests for virtualenvwrapper and trying to handle edge cases. I do not think it is particularly high priority, but I wanted to record it for posterity.

[wsanchez]

See also #53

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions.

[wsanchez]

Seems to work now:

[/tmp] wsanchez$ ./venv/bin/python -V
Python 3.7.1
[/tmp] wsanchez$ ./venv/bin/virtualenv --version
16.2.0
[/tmp] wsanchez$ ./venv/bin/virtualenv "blah "
Using real prefix '/Library/Frameworks/Python.framework/Versions/3.7'
New python executable in /private/tmp/blah /bin/python3.7
Also creating executable in /private/tmp/blah /bin/python
Installing setuptools, pip, wheel...
done.
[/tmp] wsanchez$ ./blah\ /bin/pip install tox
Collecting tox
...
Successfully installed filelock-3.0.10 pluggy-0.8.1 py-1.7.0 six-1.12.0 toml-0.10.0 tox-3.7.0 virtualenv-16.2.0
[/tmp] wsanchez$ ./blah\ /bin/tox --version
3.7.0 imported from /private/tmp/blah /lib/python3.7/site-packages/tox/__init__.py
[/tmp] wsanchez$ 

[gaborbernat]

Thanks,