On Tue, Mar 26, 2019, 09:18 Thomas Goirand <z...@debian.org> wrote: > Hi, > > Could you explain again how to fix? Maybe you can provide a patch for > this package? I'd like to fix this right after Buster, to get rid of all > traces of Python 2. >
There's no general solution. Someone needs to review the existing code documentation, convert it to some other format, and stop using Epydoc. (Or simply stop generating API documentation at all.) In my original bug report, I provided a link to the converter script that I used in my own code, which offers a starting point for one kind of solution (converting Epydoc markup to Google-style docstrings). However, there are dozens of packages that depend on Epydoc, and they are all different, so I'm not capable of providing a patch or specific instructions. KEN >
