On Mon, 29 Nov 2010 10:13:17 -0000, Jelmer Vernooij <email address hidden> wrote:
> discuss as-in a pre-implementation call of some sort, I'm a bit clueless
> as to where to start and what the best way is to add this kind of
> support into pydoctor.
Well, basically, for a C module I guess you want to insert a
pydoctor.model.Module object that describes the module you're
introspecting... here's a start, perhaps?
On Mon, 29 Nov 2010 10:13:17 -0000, Jelmer Vernooij <email address hidden> wrote:
> discuss as-in a pre-implementation call of some sort, I'm a bit clueless
> as to where to start and what the best way is to add this kind of
> support into pydoctor.
Well, basically, for a C module I guess you want to insert a model.Module object that describes the module you're
pydoctor.
introspecting... here's a start, perhaps?
lp:~mwhudson/pydoctor/introspect-c-modules
See if that makes any sense :-) You need to run like this:
.../introspect -c-modules/ bin/pydoctor \ repos/subvertpy /trunk/ subvertpy --introspect \
~/canonical/
subvertpy.client --introspect subvertpy.repos --introspect subvertpy.wc \
--html-output subvertpy-doc
from somewhere you can import subvertpy.client etc from. The output
looks like this:
http:// people. canonical. com/~mwh/ subvertpy- doc/subvertpy. repos.Repositor y.html
Hope this helps! I think it's quite good for a 20 minute hack :-)
Cheers,
mwh