On 03/02/16 19:18, Francis Poulin wrote:
Hello,
I did it both on my ubuntu and macs. For ubuntu I have
import sys print sys.executable /home/fpoulin/software/firedrake/bin/python print sys.path ['', '/home/fpoulin/software/firedrake/local/lib/python2.7/site-packages/h5py-2.5.0-py2.7-linux-x86_64.egg', '/home/fpoulin/software/firedrake/lib/python2.7/site-packages/h5py-2.5.0-py2.7-linux-x86_64.egg', '/home/fpoulin/software/pyro2', '/home/fpoulin/Code/spins/src/SPINSpy', '/home/fpoulin/software/clawpack-5.2.2', '/home/fpoulin/software/firedrake/src/firedrake', '/home/fpoulin/software/firedrake/lib/python2.7', '/home/fpoulin/software/firedrake/lib/python2.7/plat-x86_64-linux-gnu', '/home/fpoulin/software/firedrake/lib/python2.7/lib-tk', '/home/fpoulin/software/firedrake/lib/python2.7/lib-old', '/home/fpoulin/software/firedrake/lib/python2.7/lib-dynload', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/home/fpoulin/software/firedrake/local/lib/python2.7/site-packages', '/home/fpoulin/software/firedrake/lib/python2.7/site-packages']
I see that sys.executable is pointing to bin/python in my firedrake installation.
On the mac, which doesn't work, it's pointing to /user/local/opt. There is also a lot of other junk in my path that I should probably clean up. I use homebrew but clearly I'm not very able at doing things efficiently.
print sys.executable /usr/local/opt/python/bin/python2.7
Yes, I suspect this is the problem. Activating the virtualenv ought to put the virtualenv python at the beginning of PATH, but it looks like something has gone wrong here.
As for the problem that I had, I used the following:
PETSC_CONFIGURE_OPTIONS="--download-ctetgen --download-triangle --download-chaco --download-metis --download-parmetis --download-scalapack --download-hypre --download-mumps --download-netcdf --download-hdf5 --download-exodusii" 517 python firedrake-install 518 . firedrake/bin/activate 519 firedrake/bin/firedrake-update 520 firedrake-install 521 firedrake/bin/firedrake-update
It seemed strange to do firedrake-install after updating but that's what I understand the instructions to say. Maybe I misread it. If yes, I'm sorry about my confusion.
No, I agree that's what we say. I think, however, that this is a bug in our update script. This problem goes away if you run firedrake-update after *deactivating* the virtualenv. But that is very non-intuitive. I've reported this as a bug here https://github.com/firedrakeproject/firedrake/issues/690 where you can follow along. Thanks, Lawrence