I think we've seen this occasionally on new macs. I think it's caused by the virtualenv getting installed in a different python installation from the one which is being used to install Firedrake.

Try the following:

Open a new terminal (this is to try to avoid any bash path caching effects)

Type "which python". The answer you want is /usr/local/bin/python

run python and check that you can import virtualenv

If all the above works, try running firedrake-install in the new shell. If anything above fails, tell us.

Regards,

David

On Tue, 21 Mar 2017 at 10:28 Anna Kalogirou <A.Kalogirou@leeds.ac.uk> wrote:

Dear all,

I am installing firedrake on my new laptop from scratch (running macOS Sierra).

The installation script runs and installs virtualenv, up to the point where I get this:

Virtual env installed. Please run firedrake-install again.

But when I run

python firedrake-install

again, it just does the same thing (similar to the previous step) and does not install firedrake (and petsc etc..). What shall I do?

Best, Anna.