Yes, as far as I know the intention is to reduce the amount of
infrastructure that has to be maintained by Twisted developers.
Adi is doing the actual work for the migration; I only contribute
indirectly by reviewing PRs that make pydoctor integrate better with
There are efforts to make the output of pydoctor more user friendly.
This is mainly done by Tristan, but I occasionally work on it as well.
In the next major release we should have a clearer presentation of
parameter types, more navigation links and, if it's ready in time, a
side bar containing a page outline.
Thanks for the detailed explanation of what you, Adi, and Tristan
are working towards. That is a lot of hard work!
I think that using the type annotations in the code for documentation,
rather than the Epydoc @type markup tag is WAY better than what we have now.
>From what you have described, there are only a few more tasks to go before
this goal is fully completed, and the docs are published with the new pydoctor.
I'm looking forward to the end result!