Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Using virtualenv with spaces in a path

I set up a virtualenv environment on my Mac, but cannot get Pip to install packages. It fails with the following error:

/Volumes/Macintosh: bad interpreter: No such file or directory 

I tracked the problem down to there being a space in the path, as is answered here: https://stackoverflow.com/a/10873611/126564
(the path being /Volumes/Macintosh HD/Python/my_project)

But that's a bit of a problem. The proposed solution is to:

"just put your virtualenv environment in a path without a space,"

but the part with the space is the volume itself. All of my paths would have a space, unless I stored them in a directory of /. And I don't think "store your stuff outside of user space" is a good solution.

Is there a better solution to this?

like image 286
redwall_hp Avatar asked Mar 18 '13 08:03

redwall_hp


People also ask

Should I use virtualenv or VENV?

If you need the additional features that virtualenv provides over venv, then you obviously should use virtualenv. If you're satisfied with your current setup with venv, then there's no reason to choose virtualenv.


Video Answer


1 Answers

Trying this:

  • editing bin/activate, change VIRTUAL_ENV='/Volumes/Macintosh HD/Python/my_project', and change PATH="$VIRTUAL_ENV/bin:$PATH", to make it work in your environment. using echo $PATH to check if it works.
  • editing bin/pip and bin/easy_install, change first line in the two files to

    #!/usr/bin/env python

After above 2 steps, you'll make your virtualenv works(also pip/easy_install).

like image 176
Vincent Wen Avatar answered Sep 27 '22 22:09

Vincent Wen