Noah Gift wrote: > > > Cool, this is a good start, but epydoc produces some narsty looking > docs. I wonder if we might be able to take advantage of Georg Brandl's > work on enhancing the Python standard library documentation: > > http://mail.python.org/pipermail/python-dev/2007-May/073232.html > > The generated docs look gorgeous, and it would be nice if we could > fit into the general look and feel of the Python standard library > documentation. > > > That does look good...what tool did he use to do that?
It's his own code. I don't think he's done any release, but I think the code is out there somewhere if you look in the doc-sig lists. This is the codebase that I think we (Paste, Pylons) would be most interested in pursuing. I've thought about epydoc, and while I'm not opposed to it, it's not terribly appealing. You have to tweak things a lot to get something nice (no frames, better stylesheet, etc), and I don't think it has anything for stand-alone documentation. And I definitely want a toolset that does both generated and hand-written docs, with crosslinking. -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org | Write code, do good | http://topp.openplans.org/careers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
