i can create a lot better Python docs by enumerating the starting points
we care about. This incantation seems to work for me:
$ epydoc -v -u http://qpid.apache.org -n "Apache Qpid: Open Source AMQP
Enterprise Messaging" qpid.session qpid.connection qpid.datatypes
qpid.exceptions qmf.console
Jonathan Robie wrote:
Ted Ross wrote:
I seem to recall using a tool called amqp-doc (in qpid/python) to
generate pydoc-style output for the AMQP specification. This output
included the "generated" parts of the API.
Unfortunately, that tool doesn't seem to work in the latest SVN.
Ideally, I
Ted Ross wrote:
I seem to recall using a tool called amqp-doc (in qpid/python) to
generate pydoc-style output for the AMQP specification. This output
included the "generated" parts of the API.
Unfortunately, that tool doesn't seem to work in the latest SVN.
Ideally, I'd like to find a way t
Jonathan Robie wrote:
I'm trying to figure out if there is a relatively easy way to generate
more useful Python API docs.
Many of the methods you actually want to use are created when loading
the spec files at run time, and do not show up in the pydoc. That
makes it pretty hard to know what m
I'm trying to figure out if there is a relatively easy way to generate
more useful Python API docs.
Many of the methods you actually want to use are created when loading
the spec files at run time, and do not show up in the pydoc. That makes
it pretty hard to know what methods you can call by
