How do I setup a startup command for terminal in OSX?

[Zak]

I'm trying to follow this instruction: 

You will want to add the command to source /usr/local/bin/virtualenvwrapper.sh to your shell startup file, changing the path to virtualenvwrapper.sh depending on where it was installed by pip.

 But even after installing virtualenvwrapper with pip, I have no virtualenvwrapper.sh. How do I set a startup script for terminal and what command should I use?

[Doug Hellmann]

pip installs things under the same prefix where Python was installed. On my OS X system, that's in /Library/Frameworks/Python.framework/Versions/2.7/.

Where is pip running, which version of Python is it using, and where did it write the files when you installed virtualenvwrapper?

Doug

[peder]

I don't think virtualenvwrapper.sh works as it should on Mountain Lion, 

See https://bitbucket.org/dhellmann/virtualenvwrapper/issue/165/os-x-workon_home-contains-files-not-listed

[peder]

Check out this article:  http://martinbrochhaus.com/2012/07/mountain-lion.html

[TJ Marbois]

having the same problem as above... 

10.8.2

Brew python

pip install virtalenvwrapper 

trying to make it work - bash can't find virtualenvwrapper

and no file at all called virtualenvwrapper.sh on the machine after using pip to install it.... where did it go? 

source /usr/local/bin/virtualenvwrapper.sh

On Friday, September 28, 2012 5:46:57 PM UTC-4, Doug Hellmann wrote:

[Doug Hellmann]

Where is pip installed?

Doug

[TJ Marbois]

hi - ( Happy Holidays! )

 macbook$ which pip

/usr/local/share/python/pip

I got past this issue by reinstalling everything starting from easy_install -- but then I had other issues... ( heroku toolbelt screwed up ) and when I reinstalled that I lost virtualenv again.  

Any ideas?

[Doug Hellmann]

Depending on how you reinstalled, maybe you need to reinstall virtualenv? I don't use heroku, so I'm not sure how those tools work or what would have been involved in cleaning up to reinstall.

In general, the sorts of problems described in this thread are caused by not understanding where things are being installed, which is often caused by having more than one version of a tool like pip installed (especially for different versions of python).

Doug

[TJ Marbois]

Doug

Thanks - Im reinstalling virtualenvwrapper

macbook$ pip install virtualenvwrapper

Requirement already satisfied (use --upgrade to upgrade): virtualenvwrapper in /usr/local/lib/python2.7/site-packages

Requirement already satisfied (use --upgrade to upgrade): virtualenv in /usr/local/lib/python2.7/site-packages (from virtualenvwrapper)

Requirement already satisfied (use --upgrade to upgrade): virtualenv-clone in /usr/local/lib/python2.7/site-packages (from virtualenvwrapper)

Requirement already satisfied (use --upgrade to upgrade): stevedore in /usr/local/lib/python2.7/site-packages (from virtualenvwrapper)

Requirement already satisfied (use --upgrade to upgrade): distribute in /usr/local/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg (from stevedore->virtualenvwrapper)

Cleaning up...

its already there from previous - so something else got changed in between.

when I which virtualenvwrapper - I get no reply.

and Im back to square one again of not knowing where the virtualenvwrapper.sh is supposed to be sourced from?

$ export WORKON_HOME=~/Envs
$ mkdir -p $WORKON_HOME
$ source /usr/local/bin/virtualenvwrapper.sh

I get this:

macbook$ export WORKON_HOME=~/Envs

macbook$ source /usr/local/bin/virtualenvwrapper.sh

-bash: /usr/local/bin/virtualenvwrapper.sh: No such file or directory

[TJ Marbois]

I dont see virtualenvwrapper.sh 

macBook-Pro:site-packages macbook$ ls

clonevirtualenv.py setuptools-0.6c11-py2.7.egg-info stevedore-0.7.2-py2.7.egg-info virtualenv_support

clonevirtualenv.pyc setuptools.pth virtualenv-1.8.4-py2.7.egg-info virtualenvwrapper

distribute-0.6.32-py2.7.egg sitecustomize.py virtualenv.py virtualenvwrapper-3.6-py2.7-nspkg.pth

easy-install.pth sitecustomize.pyc virtualenv.pyc virtualenvwrapper-3.6-py2.7.egg-info

pip-1.2.1-py2.7.egg stevedore virtualenv_clone-0.2.4-py2.7.egg-info

macBook-Pro:site-packages macbook$ cd virtualenvwrapper

macBook-Pro:virtualenvwrapper macbook$ ls

hook_loader.py hook_loader.pyc project.py project.pyc user_scripts.py user_scripts.pyc

macBook-Pro:virtualenvwrapper macbook$ pwd

/usr/local/lib/python2.7/site-packages/virtualenvwrapper

macBook-Pro:virtualenvwrapper macbook$ 

On Monday, December 24, 2012 12:46:42 PM UTC-5, Doug Hellmann wrote: