move python bindings
It was decided to move the Python bindings from dune-python into the core modules. A few things that need to be decided on:
- I would like to keep the folder structure of
dune-foo/python/dune/foo
for the python parts of the bindings as is otherwise there would have to be a lot of change - At the moment the C++ parts of the bindings are located in
dune-python/dune/python/common|grdi|...
which made sense for thedune-python
module. For the core this would mean havingdune-common/dune/python/common
. Is that acceptable? We could decide to switch todune-common/dune/common/python
(changing all the included will be a bit painful...) - As we started
pybind11
was undergoing major changes on a regular basis so we decided to include a copy ofpybind11
indune-python/dune/python/pybind11
and updating it when interesting new feature got added topybind11
. It's header only about 600K - here is the licence https://github.com/pybind/pybind11/blob/master/LICENSE It simplifies maintenance and users do not have to first install pybind11 (I don't it's packaged but I'm not sure). Can we keep it that way (for now), i.e. includepybind11
indune-common
?
That is all I can think of for now