pip when used with virtualenv will generally install packages in the path <virtualenv_name>/lib/<python_ver>/site-packages. For example, I created a test virtualenv named venv_test with Python 2.7, and the django folder is in venv_test/lib/python2.7/site-packages/django.
simply run Update after OP’s edit: There was a bug in the OP’s version of virtualenv, as described here. The problem was fixed by running:
This works for me: –no-index – Ignore package index (only looking at –find-links URLs instead). -f, –find-links <URL> – If a URL or path to an HTML file, then parse for links to archives. If a local path or file:// URL that’s a directory, then look for archives in the directory listing.ShareImprove this answer Follow … Read more
Having tested this using Python 3.5 and pip 7.1.2 on Linux, the situation appears to be this: pip install –user somepackage installs to $HOME/.local, and uninstalling it does work using pip uninstall somepackage. This is true whether or not somepackage is also installed system-wide at the same time. If the package is installed at both … Read more
First make sure you have checked the most voted answer. I’m not sure if it’s exactly your problem, but in my case, I wasn’t able to upgrade Django to 1.2.4 – I was always finishing with 1.2.3 version, so I uninstalled Django with: Then I removed <virtualenv>/build/Django directory and finally I installed the proper version with:
pip is just a PyPI package like any other; you could use it to upgrade itself the same way you would upgrade any package: On Windows the recommended command is:
pip is just a PyPI package like any other; you could use it to upgrade itself the same way you would upgrade any package: On Windows the recommended command is:
1170 pip is just a PyPI package like any other; you could use it to upgrade itself the same way you would upgrade any package: On Windows the recommended command is: