Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • That's right, homebrew is installed. It seems like it is installed with both, could it cause a problem? I though that the interpreter crawls my PYTHONPATH and use the first virtualenv he finds.
    – vmonteco
    Commented Jul 7, 2015 at 16:55
  • I don't use virtualenvwrapper but it seems the virtualenvwrapper.sh script that is sourced determines which python interpreter to use before exporting the wrapper functions to your current environment.
    – Josh J
    Commented Jul 7, 2015 at 16:56
  • You mean the virtualenvwrapper.sh ?
    – vmonteco
    Commented Jul 7, 2015 at 16:58
  • I did, sorry. I clarified the above comment.
    – Josh J
    Commented Jul 7, 2015 at 16:59
  • Ah, this script's purpose is to define some functions in bash, such as "workon". You have its source here : bitbucket.org/dhellmann/virtualenvwrapper/src/…
    – vmonteco
    Commented Jul 7, 2015 at 17:05