-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to find virtualenvwrapper.sh #39
Comments
I have just started the tutorials and ran into this problem. Any idea on what to do about it? I am running OS X 10.8 and have default Python install as well as 2.7 & 3.3. EDIT: I figured it out. I couldn't find virtualenvwrapper.sh anywhere on my hard drive using procedures that I am used to (total terminal noob). But found this on stack overflow: http://stackoverflow.com/questions/12647266/where-is-virtualenvwrapper-sh-after-pip-install. I used '$ which virtualenvwrapper.sh' to find the file and then copied it into /usr/local/bin/ |
Aside: it’s misleading if virtualenvwrapper.sh is installed as a script (i.e. in a bin directory and with the execute bit), as it’s a file meant to be sourced. People are often confused by how virtualenv works, and virtualenvwrapper makes it more handy but more confusing. I’ve wanted to give a lightning talk or write something about that for some time; I should see if I can propose additional text to the relevant section in newcoder. |
More info from duplicate ticket #83: From @sullyj3: on arch, virtualenvwrapper.sh doesn't seem to be located in /usr/local/bin, but rather both /usr/bin and /bin From me: It’s in yet another place on Debian and derived systems such as Ubuntu: http://askubuntu.com/questions/251378/where-is-virtualenvwrapper-sh |
@econchick You closed this ticket as duplicate (of #83 I assume), but the other ticket was already closed as duplicate of this one. |
I closed it because I added a fix for it.
|
Ah! :‑) |
Add directions to find the script file after pip installs it.
Mostly issues with Ubuntu, and Mac w/ more than one Python version.
The text was updated successfully, but these errors were encountered: