virtualenvwrapper

I have a python program I want to install into my virtualenv - it's a zip package that I need to unzip and then run a setup.py program - but my question is more regarding how to get these unzipped files into my virtualenv so that the package gets installed into the virtualenv's site-packages folder? I can also install from inside my virtualenv using pip install <package name> , but for some reason, the package that PIP downloads is out of date. So - can someone tell me a few easy steps for installing a package manually? So far I have the basic commands to load up the Virtualenv: -bash-3.2$

Apologies if this is a basic question: I have been trying to setup Python on my laptop by following the tutorial here . Under PIP, VIRTUALENV + VIRTUALENVWRAPPER subtitle, it says And now setup virtualenvwrapper: 1 $ export WORKON_HOME=$HOME/.virtualenvs 2 $ export MSYS_HOME=/c/msys/1.0 3 $ source /usr/local/bin/virtualenvwrapper.sh The last line of above gives me the following error: $ source /usr/local/bin/virtualenvwrapper.sh sh.exe": /usr/local/bin/virtualenvwrapper.sh: No such file or directory So when I test my setup I get the following error: $ mkvirtualenv TestEnv sh.exe": mkvirtualenv

pip recognize global installed packages..?! :-( I've used virtualenvwrapper preactivate hook to clean PYTHONPATH, export PYTHONPATH="" then echo $PYTHONPATH returns empty string, but this didn't help. What's wrong? bentzy@lama:~$ mkvirtualenv test New python executable in test/bin/python Installing setuptools............done. Installing pip...............done. virtualenvwrapper.user_scripts creating /home/bentzy/.virtualenvs/test/bin/predeactivate virtualenvwrapper.user_scripts creating /home/bentzy/.virtualenvs/test/bin/postdeactivate virtualenvwrapper.user_scripts creating /home/bentzy/

This question already has an answer here: Renaming a virtualenv folder without breaking it 8 answers I kept looking for answer but didn't find one. I have a virtual env dir, a project dir with a req.txt. When I run pip -r req.txt, it installs some apps from github (source) and some from pypi. The ones from pypi are fine after relocatable call on the virtual evn, however the links in the site-packages for the apps that it installed from github still point to the old directory location. Anyone else has seen this behavior? Any quick way around it? Also, relocatable is not honoring the --no-site

Is it possible to force virtualenv to use the latest setuptools and pip available from pypi? Essentially, I'm looking for the opposite of the --never-download flag. Currently, when I make a new virtualenv, it uses the local (old) versions that come bundled with virtualenv. $ v.mk testvenv New python executable in testvenv/bin/python Installing setuptools............done. Installing pip...............done. $ pip show setuptools --- Name: setuptools Version: 0.6c11 Location: /Users/cwilson/.virtualenvs/testvenv/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg Requires: $ pip search

In brief, my problem is that when I try to create a virtualenv using mkvirtualenv from virtualenvwrapper, I get the following error: $ mkvirtualenv test New python executable in test/bin/python ERROR: The executable test/bin/python could not be run: [Errno 13] Permission denied However, when I look at the permissions for the binary, as far as I can tell, everything should be fine... $ ll ~/.virtualenvs/test/bin total 2604 drwxr-xr-x 1 (username) staff 5 Feb 7 19:10 ./ drwxr-xr-x 1 (username) staff 5 Feb 7 18:51 ../ -rwxr-xr-x 1 (username) staff 2655776 Feb 7 19:10 python* lrwxrwxrwx 1

After upgrading to OSX Mavericks, I am getting this message in the terminal: /usr/bin/python: No module named virtualenvwrapper virtualenvwrapper.sh: There was a problem running the initialization hooks. If Python could not import the module virtualenvwrapper.hook_loader, check that virtualenv has been installed for VIRTUALENVWRAPPER_PYTHON=/usr/bin/python and that PATH is set properly. Try reinstalling pip and then reinstalling virtualenvwrapper (I had to go through these steps after upgrading to Mavericks): $ sudo easy_install pip $ sudo pip install --upgrade virtualenvwrapper Josh Antweiler

How do you change the default Virtualenvwrapper prompt? By default, working on a particular virtual environment with a command like "workon <_name_of_env_>" prepends the name of the virtualenv to your prompt. This may work poorly if you're not using a default command prompt. ivanalejandro0 If you are working on a custom PS1 (as I when found out this issue), I recommend you to disable prompt change, use export VIRTUAL_ENV_DISABLE_PROMPT=1 (see virtualenv docs ), and make your own virtualenv prompt in order to add to your PS1. See this snippet that I've used: function virtualenv_info(){ # Get