Found the issue: my PYTHONPATH was set. Unsetting it solved the problem. Shouldn't `activate` handle the PYTHONPATH?
On Sunday, November 6, 2016 at 9:22:01 PM UTC+11, Alec Taylor wrote: > > Running Ubuntu 16.10 with Python 2.7.12+ (default one) and virtualenv > 15.0.3 (`sudo -H pip install virtualenv`). I've also tried with the `sudo > apt install python-virtualenv virtualenv` version. What am I doing wrong? > > $ virtualenv a && . "$_"/bin/activate && pip --version > New python executable in /tmp/a/bin/python > Installing setuptools, pip, wheel...done. > pip 9.0.0 from /usr/local/lib/python2.7/dist-packages (python 2.7) > $ /tmp/a/bin/pip --version > pip 9.0.0 from /usr/local/lib/python2.7/dist-packages (python 2.7) > $ /tmp/a/bin/python -c 'from pip import __file__; print __file__' > /usr/local/lib/python2.7/dist-packages/pip/__init__.pyc > > PS: Running with regular Bash 4.3.46(1)-release in GNOME Terminal. When I > activate the virtualenv this appears in my env output: VIRTUAL_ENV=/tmp/a > > PPS: Cross-posted [yesterday] http://stackoverflow.com/q/40438089 > -- You received this message because you are subscribed to the Google Groups "virtualenv" group. To unsubscribe from this group and stop receiving emails from it, send an email to python-virtualenv+unsubscr...@googlegroups.com. To post to this group, send email to python-virtualenv@googlegroups.com. Visit this group at https://groups.google.com/group/python-virtualenv. For more options, visit https://groups.google.com/d/optout.
