Use -e options with pip for dev-env builds?

[Lizao Li]

Currently the fenics-build install python based packages using the standard pip install, which copies the source to the installation directory. For development, there is python setup.py develop or pip install -e which only links the source to the installation directory. This way the developer can work on the git source and debug the code without reinstalling every time. Isn't this more intuitive as defaults for dev builds?

[Prof Garth Wells]

Maybe, we'd need to fix https://bitbucket.org/fenics-project/ffc/issues/115 first.

[Lizao Li]

Indeed. I just encountered that problem myself...

[Jack Hale]

Sounds good, need to get the pip -e working first though clearly!

[Prof Garth Wells]

The blocking issue (https://bitbucket.org/fenics-project/ffc/issues/115) has been resolved.

I'm indifferent on whether or not this is a good idea. Reasoning is that we shouldn't aim for an environment that is tailored for every dev - the images should be a starting point for developers to craft their own environment(s).

[Prof Garth Wells]

Closing this. Can be re-opened if there is interest.