[Python-apps-team] Bug#932584: Epydoc and Pydoctor

Ian Jackson ijackson at chiark.greenend.org.uk
Wed Jul 31 16:46:34 BST 2019


Kenneth Pronovici writes ("Epydoc and Pydoctor"):
> (I'm the maintainer for epydoc.)

Hi.

Thanks for the analysis which seems to make sense to me.

> Given that epydoc does not work properly in Python 3, and it's beyond
> my capabilities to fix it, there aren't too many options here.  Either
> we remove pydoctor's dependency on epydoc, or we remove pydoctor from
> the archive.
> 
> I don't see any evidence that upstream is developing a Python 3
> version of this code.  This means that python-pydoctor will have to be
> removed from the archive eventually.   Maybe now is the time to do it?

I had a quick look at Sources in some random sid chroot and the
following Build-Depend on it:
  git-buildpackage
  kiwi
  libcloud
  subvertpy
(and there are no rdepends).

AFAICT pydoctor was written for Twisted but Twisted no longer seems to
use it ?  But here
  https://wiki.python.org/moin/DocumentationTools
it is still listed and not in the dead section.  The Python 3 issue
  https://github.com/twisted/pydoctor/issues/96
is not encouraging.

IDK if anyone here is in close enough contact with the upstream Python
world to know whether pydoctor is dead or not.

> Otherwise, I will see if I can determine how well the package works
> without epydoc installed.  If it works (i.e. doesn't blow up) and I
> don't hear back with other instructions, I will eventually NMU my
> changes to remove the epydoc dependency.   Given that I haven't gotten
> any replies for more than 18 months now, I won't wait that long before
> doing this NMU.

That sounds really good to me for now.  I think you can do this NMU
whenever you like.

Ian.

-- 
Ian Jackson <ijackson at chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.



More information about the Python-apps-team mailing list