I think this could be made automatic, thanks to the execve system call (wrapped by os.exec* in Python). ________________________________ From: firedrake-bounces@imperial.ac.uk [firedrake-bounces@imperial.ac.uk] on behalf of Colin Cotter [colin.cotter@imperial.ac.uk] Sent: 03 November 2015 15:05 To: firedrake Subject: Re: [firedrake] Mac install The problem here is that a different python is used to execute the script the first time than the second, so really the script needs to die after the virtualenv is created. (as suggested by Lawrence). I fixed this by removing the firedrake directory, and re-running the script. cheers --cjc On 31 October 2015 at 10:49, Colin Cotter <colin.cotter@imperial.ac.uk<mailto:colin.cotter@imperial.ac.uk>> wrote: Dear all, Just attempted an install script on a clean Mac with El Capitan. After running the install script I was instructed to run it again, and got the following message: Creating firedrake virtualenv. ERROR: The executable firedrake/bin/python2.7 is not functioning ERROR: It thinks sys.prefix is u'/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7' (should be u'/Users/colincotter/firedrake') ERROR: virtualenv is not compatible with this system or executable cheers --cjc