> > > > That does look good...what tool did he use to do that?
Jonathan LaCour " >From what I can tell, its a tool of his own creation. I might send him > and email and find out if I can get access to the code somehow, and if > it might be usable for TurboGears. > > In my opinion, Python is really lacking a good documentation system, and > Georg's work looks like it might be the thing to solve that problem. > If we can find a way to use it, maybe we can blaze a trail for other > projects. " > Ian Bicking: " 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. > " Lets be careful here guys...two python web application frameworks have just merged, and next we are talking about fixing globally python documentation generation....these are dangerous ideas, from dangerous subversive minds........in other words keep up the good work. Next thing you know someone is going to fork django and make it wsgi compatible :) -- http://www.blog.noahgift.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
