Yes, atelier simplifies my life but for you it makes things more difficult to understand...
I guess that you should have a look at the atelier.sphinxconf.configure() function: https://github.com/lino-framework/atelier/blob/master/atelier/sphinxconf/__init__.py#L64 configure() updates the globals() namespace of the conf.py file, so when it does *globals_dict.update(foo='bar')* then that's as if you would type *foo='bar'* in your conf.py file. Quick translated excerpt of autosummary options that might be relevant for you: autodoc_default_options={ 'members': None, 'show-inheritance': None} autodoc_member_order='bysource' autodoc_inherit_docstrings=False HTH Luc On 03.10.2018 14:44, [email protected] wrote: > Dear Luc, > > thank you for this valuable hint. Your example doc looks awesome and > exactly as this what was in my mind. > > The test with my own code did not work. > https://gitlab.com/buhtz/buhtz-sphinx > I always do a "make html" in the doc-directory to generate the doc. > > But I have not copied your conf.py exactly. > https://gitlab.com/buhtz/buhtz-sphinx/blob/master/doc/source/conf.py > Because I didn't understand all details of your conf.py. What is this > with the "import atelier" in it? Why do you use the package that should > be documented in your conf.py file? > You also use a lot more atelier calls in the conf.py file. > > It would help my understanding to see a minimal example. > > The sphinx-doc website about autosummary doesn't explain how to > configure a complete project environment to run. > . > -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
