Here's the virtualenvwrapper section in my .bash_profile#Virtualenvwrapper settingsexport WORKON_HOME=/Users/mike/Virtualenvsexport PROJECT_HOME=/Users/mike/Developer/Pythonexport VIRTUALENVWRAPPER_VIRTUALENV_ARGS='--no-site-packages'source /usr/local/bin/virtualenvwrapper.sh
On Tuesday, October 7, 2014 8:04:52 AM UTC-5, Doug Hellmann wrote:
On Oct 5, 2014, at 3:48 PM, Mike Beatty <mik...@gmail.com> wrote:
> Like other users, my Mac's home directory is on a secondary drive which results in a path with a space in it. e.g. /Volumes/Macintosh HD/Users/<username>/
> I've found that when creating and activating the virtualenv, if I try to run pip I get a Bad Interpreter error because the shebang line in the pip script contains that path with a space. To get around this I created a symlink to /Users/<username> on my root drive and when I create a vrtualenv, i type out the full path to my virtualenv directory and it creates the shebang properly.
> I was hoping that virtualenvwrapper would help be get around having to type the full path but unfortunately, even after adding
> export WORKON_HOME="Users/<username>/Virtualenvs" to .bash_profile, the shebangs are created with the full /Volumes/Macintosh HD/ path.
> Am I wrong in thinking that mkvirtualenv should honor the path in WORKON_HOME when creating the virtualenv? Is there some other way to force mkvirtualenv to user the symlink path?
Looking at virtualenvwrapper_derive_workon_home, it seems like what you’re doing should work. Can you post the actual text from your login script?