I'm having trouble with Paver's documentation generated via autodoc
for some modules, and I wondered if there's any useful suggestions for
how to approach this problem. I admit that I haven't looked at the
autodoc code yet.
A Paver Task looks like this:
@task
def my_task():
"Foo"
pass
Paver 0.8 used decorators just to store information in a registry and
the function object itself was left alone. With Paver 1.0, the
functions are truly decorated with a new callable. The callable that
replaces the original function has its __doc__ set to the function's
__doc__. (I also tried using functools.update_wrapper to set things).
I'm thinking that autodoc is just skipping over these objects because
they're not actual "Function" objects any more. Is that the case?
Would it be reasonable to just document anything that's callable?
Kevin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sphinx-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sphinx-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
