Separation of dune and python code
As the exastencil people now started to also use the form compiler and write their own backend, we discussed that it would be nice to have the genetic part as a separate python module which can be pip installed.
Jan, Rene and Marcel already invested some work to ensure that the fine build system is not needed.
To fully separate the two parts the plan would be:
- split the repo, but keep the history
- include
python/dune/codegen
as a submodule - get rid of the dependency on dune-testtools in the genetic python part
- keep most dune parts in the python module
- keep the cake integration in dune-codegen
- find a new name for the python module (current suggestion was
xfc
eXtendable Form Compiler)
We (@christi, @marcel.koch, @rhess) believe that the effort is moderate, while it would make the project more inviting for other groups.
What are the opinions? (I'm asking in particular @dominic)