
Unfortunately, on a first look pydoc makes this hard (by returning string values to build a result). I have to take a deeper look whether it's possible.
Still, there is sometimes a description element and sometimes not. And it's not clear why.
* class/@parents should be @bases (cf. __bases__)
OK.
Changed and committed. Also added optional doctype & encoding. I also added my own versions of stylesheet & css, the stylesheet takes parameters and is thus easily adapted to dynamic page generation. Ciao, Jürgen -- Jürgen Hermann, Developer (jhe@webde-ag.de) WEB.DE AG, http://webde-ag.de/

Jürgen Hermann wrote:
Well, we don't use pydoc except for infrastructure. The way to do it would be to pass a file-like object to the various documentation functions, so they write to it instead of returning a string.
Still, there is sometimes a description element and sometimes not. And it's not clear why.
Err... good question. Ok, let's use a description element for everything.
Oh, good, I wasn't sure how to do that with XSLT. Can you put up an example of the output?

Jürgen Hermann wrote:
Well, we don't use pydoc except for infrastructure. The way to do it would be to pass a file-like object to the various documentation functions, so they write to it instead of returning a string.
Still, there is sometimes a description element and sometimes not. And it's not clear why.
Err... good question. Ok, let's use a description element for everything.
Oh, good, I wasn't sure how to do that with XSLT. Can you put up an example of the output?
participants (2)
-
Itamar Shtull-Trauring
-
Jürgen Hermann