For a literal include (would be so much better) we would need
the path from CMake somehow passed to sphinx...

Construction of parallel grids will be properly addressed in the near future.

[bugfix] Only run tutorial if dune-grid is found.



See merge request !71

Feature/more python doc

Improve documentation of the python module inside testtools.

* [x] Document all methods at least with a simple docstring
* [ ] Tell autosummary not to document imported modules?

Fixes #84 

See merge request !70

TODO: We need to host the documentation on the dune website.
Automated documentation tools seem to be too focused on
python modules only. Our documentation buildprocess is too
complicated for them.

This currently only works with the dune-python branch
feature/export-python-source-path

Document classes inside modules

Module documentary will be generated with a summary
followed by all functions documented with autofunction
under their function name. Each function has to toctree
entry.

Dominic Kempf authored Dec 04, 2015 and Timo Koch committed Dec 15, 2015

This turned out to be much more painfil than I thought it would.
The reason: Sphinx does not know namespace packages (quite a bummer).
As a consequence:
* We will not be able to use `sphinx-apidoc`
* We do not get rid of the errors about not finding `dune.common.x`
  (it thinks it should be in the scope of the documented module, but its not)

I have renamed the former file `dune-testtools.rst` to `python.rst`.
Use this file for the python docs and include it into the index
toctree at will.

[CMake] Add a metatarget that groups all static variants

This fixes #102 

Works quite nicely, actually!

See merge request !69