[Doc-SIG] alternatives to epydoc?
fuzzyman at voidspace.org.uk
Thu Oct 7 14:12:12 CEST 2010
On 07/10/2010 13:08, INADA Naoki wrote:
> bzr [#1] uses pydoctor [#2] for api reference [#3].
> [#1] http://bazaar.canonical.com/
> [#2] http://codespeak.net/~mwh/pydoctor/
> [#3] http://people.canonical.com/~mwh/bzrlibapi/
These days all the cool kids* are using Sphinx and the autodoc extension:
All the best,
* I'm not one of the cool kids unfortunately... I still tend to think
that documentation and docstrings are two different things.
> On Thu, Oct 7, 2010 at 1:52 AM, Bill Janssen<janssen at parc.com> wrote:
>> I've been documenting UpLib with a combo of ReST for the standalone
>> docs, and epydoc for the API documentation. But epydoc seems to be
>> dying a slow death of non-maintenance. It won't work with docutils 0.6
>> or 0.7, and Python 2.6 seems to crash when running it.
>> So, I'm looking for an alternative to epydoc. Preferably something
>> easy to convert to... Any pointers?
>> Doc-SIG maillist - Doc-SIG at python.org
READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
More information about the Doc-SIG