> This has some layers to it -- autodoc directives generate reST again. > Which means that you'd have to override the class directive's behavior > when parsing its signature. > > Look at the parse_signature method of PythonDesc in sphinx.directives.desc. > You will have to override that and re-register the "class" directive. > > Be advised though that these APIs will change dramatically in Sphinx 1.0; > you may want to wait for it before experimenting. Thanks, I will try this. Hg trunk is what will become eventually 1.0, right? > That said, why don't you add that info in the body? Being the most important think, it warrants place in the header itself. Inheritance diagrams don't work for me (they just don't produce anything), and this is a nice way to show it somehow (I will bug you with inheritance diagrams separately, as I try it out more; I suspect (again) boost::python vs. pure python classes.)
Cheers, Vaclav -- 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.
