… And now merged, with API documentation now published automatically at


> > The autodoc API documentation needs to learn not
> > to pick up some private members that are uninteresting while we need to
> > keep others present since they are base classes and the only documentation
> > for some subclasses is within those base classes. The input of those with
> > more sphinx experience would be great about now!
> This problem remains -- some "_hiddden" classes and functions need to be
> included in the API docs to be meaningful at all while others are most
> unwelcome.
> Help needed!
> > Is it worth putting these files into a new python-debian-doc binary
> > package?
> My feeling is that if the apidocs are useful enough to put on a website,
> they are useful enough to put in a package.


Stuart Prescott    http://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/         stu...@debian.org
GPG fingerprint    90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Reply via email to