> First, that's very speculative. Second, that's upstream's problem.
> The upstream Makefile and conf.py are likely generated by Sphinx itself
> via sphinx-quickstart. Did your upstream tinker with them that much that
> they cannot be trusted?
No this is just that does not fit well with extension.
> Some upstream do use a build_sphinx command, but it is far from common
> and it does not solve the extension module problem.
Yes this is what they are doing. extension are part of the python ec-system but
it seems thaht this is not well suported out of the box by sphinx.
# If extensions (or modules to document with autodoc) are in another directory,
# add these directories to sys.path here. If the directory is relative to the
# documentation root, use os.path.abspath to make it absolute, like shown here.
#
# import os
# import sys
# sys.path.insert(0, os.path.abspath('.'))
You need to customize the sys.path in order to find the extensions.
This path can change depending on the setup.py build options so this is not
reliable.
> Why? All you need is *one* occurrence of the extension modules somewhere
> in the PYTHONPATH in order to generate the docs. Chances are that's how
> upstream generates them.
Because by experience I find issue in the build system and the python code when
building the doc for multiple
interpreter (python2/python3 differences...)
> > Found a total of 643 reverse build-depend(s) for python-all-dev.
> >
> > not that small
> How is the ratio over all the Python packages? I suspect very small.
Found a total of 1968 reverse build-depend(s) for python-all.
not that small 32 % ;)
Cheers
Fred
