Timeline for PYTHONPATH interfering with virtualenv
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2020 at 9:12 | history | edited | Community Bot |
Commonmark migration
|
|
| Dec 18, 2014 at 16:17 | vote | accept | cjohnson318 | ||
| Dec 18, 2014 at 8:47 | comment | added | Simeon Visser | Those are the Python versions I use: the Python/pip outside the virtualenv and those inside. I think that's the aim: for Python/IPython to have the same deps outside the venv, so they'd share what pip installs | |
| Dec 18, 2014 at 0:56 | comment | added | cjohnson318 |
Are you sure? Python and pip are both located in /usr/local/bin/ and pip, by default, installs things elsewhere. Putting everything in /usr/local/bin seems counterintuitive.
|
|
| Dec 18, 2014 at 0:11 | comment | added | Simeon Visser |
Run which python and which pip and use that location for installating Python packages that don't belong to a virtualenv. For everything else, use virtualenv and install packages inside the virtualenv. So, short answer, most of your packages should be inside a virtualenv and only a few outside.
|
|
| Dec 17, 2014 at 23:57 | comment | added | cjohnson318 |
Should I move all of my Python packages to /Library/Python/2.7/site-packages? That seems a bit hacky too because setuptools and pip seem to install everything in /usr/local/lib/python2.7/site-packages.
|
|
| Dec 17, 2014 at 23:52 | comment | added | pcurry | I second that brew, pip, and virtualenv interact painfully. | |
| Dec 17, 2014 at 23:48 | history | answered | Simeon Visser | CC BY-SA 3.0 |