Skip to content
Advertisement

Tag: virtualenv

Virtualenv uses wrong python, even though it is first in $PATH

I had a problem where python was not finding modules installed by pip while in the virtualenv. I have narrowed it down, and found that when I call python when my virtualenv in activated, it still reaches out to /usr/bin/python instead of /home/liam/dev/.virtualenvs/noots/bin/python. When I use which python in the virtualenv I get: /home/liam/dev/.virtualenvs/noots/bin/python When I look up my $PATH

Concept of Virtual Environments

Hope this question belongs here. As a linux noob, I am sure my question sounds confusing and heavily non-technical, but please help me understand this. Anaconda Python Distribution comes with the concept of creating environments where I can maintain a variety of python versions and specific packages based on my need. Without disturbing other versions and their modules! rbenv does

Advertisement