Given the  news that Pudge fails on TurboGears as it stands, and that
some extra work would be require with PythonDoc, along with the fact
that Jorge has made epyDoc work in the past, I vote that we create the
docs with epydoc and move on with our lives.

Anybody who's interested in getting PythonDoc or Pudge to work is
welcome to try to make that happen in the future, but unless you're
willing to do it this week, I think we should go with the best known
candidate, with the option of changing later if somebody is willing to
create something that looks nicer, or works better.

--Mark Ramm

On 1/9/07, Ken Kuhlman <[EMAIL PROTECTED]> wrote:
>
> I'm definitely no expert either, but shouldn't Pudge at least be on the
> list of possible api doc tools?
>
> Some projects that I've seen using it:  Kid, SQLObject, Pylons,
> Migrate... not to mention ToscaWidgets.org appears to have been built
> with it.
>
> Pudge was death's door for a long time, but last month Ben Bangert
> announced that he plans "on maintaining pudge for the foreseeable
> future, or until a better documentation system comes along ..."
>
> http://groups.google.com/group/pylons-discuss/browse_frm/thread/28af1f2033996702/4fa3cc9791ef44eb?lnk=gst&q=pudge&rnum=1#4fa3cc9791ef44eb
>
>
> Of course, most of the links on pudge.lesscode.org are dead, and there
> hasn't been a post on it's list in almost a year, so the project's
> still not healthy.   On the other hand, a new release has been made &
> it's available from the Cheeseshop, so it's at least out of it's coma
> now.
>
>
> >
>


-- 
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"TurboGears Docs" 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-docs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to