-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 25.02.2010 10:05, schrieb Václav ?milauer: >> 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?
No, actually that will be http://bitbucket.org/birkenfeld/sphinx-domains/. I didn't merge that into trunk until now because many people use trunk instead of 0.6.x, and an unstable API would be bad for them. The day of the merge back into trunk is coming soon, however :) >> 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.) Quite possible :( That said, if you find out an easy way to determine if an object is a boost::python class (and if a function is a boost::python function, from the other thread), let me know and I'll add it to autodoc. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkuKK7IACgkQN9GcIYhpnLCEbwCgiXzW/x8MNERRx74DbSu+UZuD CN0An0hcHhg+zWr/NV3d6plWMz87v7ic =6Cz1 -----END PGP SIGNATURE----- -- 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.
