`pipenv shell` fails with path including spaces.

tsbertalan@sindri:~$ sudo pip install pipenv
... snip ...
tsbertalan@sindri:~$ cd dirname\ with\ spaces/
tsbertalan@sindri:~/dirname with spaces$ pipenv shell
Creating a Pipfile for this project...
Creating a virtualenv for this project...
New python executable in /home/tsbertalan/dirname with spaces/.venv/bin/python
Installing setuptools, pip, wheel...done.

Virtualenv location: /home/tsbertalan/dirname with spaces/.venv
Spawning environment shell (/bin/bash).
/bin/bash: /home/tsbertalan/dirname: No such file or directory
tsbertalan@sindri:~$ cd dirname\ with\ spaces/
tsbertalan@sindri:~/dirname with spaces$ pipenv shell
Creating a Pipfile for this project...
Creating a virtualenv for this project...
New python executable in /home/tsbertalan/dirname with spaces/.venv/bin/python
Installing setuptools, pip, wheel...done.

Virtualenv location: /home/tsbertalan/dirname with spaces/.venv
Spawning environment shell (/bin/bash).
/bin/bash: /home/tsbertalan/dirname: No such file or directory

[nateprewitt]

I’m going to leave this here for when someone eventually searches trying to solve this issue. While #99 solves the pipenv activation issue, most other pipenv commands still don’t work properly. After a couple hours of pulling threads, I came across this.

virtualenv, and thus pipenv, calls the absolute path to the .venv directory to run things like pip and python. Since these have a space in their path, the the linux exec call will always treat the first space it encounters as the end of the command. Anything after that is considered a parameter. This means anything in the form /home/user/path to dir/.venv/bin/pip won’t work.

So in order to address this, we’d need to allow the user to provide an alternative path for installing the virtualenv and then track that somewhere. That seems a bit excessive for a likely uncommon, and fairly avoidable, edge case. If it proves to be a significant problem, that’s probably the best route to go though. Until then, I don’t think we can support paths with spaces in a meaningful way.

[jessebraham]

@kfirbreger At this point Windows is not officially supported, so it was not something that was taken in to consideration. If Windows support is added then yes it will need to be changed.