On 5 Feb 2016, at 13:27, Francis Poulin <fpoulin@uwaterloo.ca> wrote:
Thanks Lawrence. Below are my results.
** regular ** Francis-Poulins-MacBook-Pro:~ fpoulin$ which python Francis-Poulins-MacBook-Pro:~ fpoulin$ python -c "import sys; print sys.executable; print sys.path" /usr/local/opt/python/bin/python2.7
...
** virtualenv **
Francis-Poulins-MacBook-Pro:~ fpoulin$ cd ~/software/ Francis-Poulins-MacBook-Pro:software fpoulin$ source firedrake/bin/activate (firedrake)Francis-Poulins-MacBook-Pro:software fpoulin$ which python /Users/fpoulin/software/firedrake/bin/python (firedrake)Francis-Poulins-MacBook-Pro:software fpoulin$ python -c "import sys; print sys.executable; print sys.path" /usr/local/opt/python/bin/python2.7
... This is the bit that's wrong, I think. Although your shell thinks that python is the python executable in the virtualenv, when you launch python, it's the same as if you had not activated the virtualenv. If you run /Users/fpoulin/software/firedrake/bin/python -c "import sys; print sys.executable; print sys.path" What do you get? Additionally, before and after virtualenv activation, what does. $ python -c "import sys; print sys.version" say? And also, before and after virtualenv activation, what is: $ env Thanks, Lawrence