I think we should use pudge for API doc generation, and I want to be fairly hard-core about getting good docstrings, comments and an API overview together so new developers can jump into TG2 development quickly.
My reasoning for picking Pudge is simple -- it's what's used in pylons, paste, and other sub-projects. --Mark On 6/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > On 6月28日, 上午1時53分, "Mark Ramm" <[EMAIL PROTECTED]> wrote: > > > Yes, we actually require the current svn version, as we had to fix a bug > > > in the Buffet template API handling in Pylons. > > > > I also understand (from Ben) that there are also some other changes to > > the way Routes and the pylons controllers (which we inherit from) work > > in pylons trunk would make our lives easier, so we started out with > > trunk in the first place. > > > > We also want to track with Pylons as they add Babel support, and the > > new database configuration stuff. > > > > --Mark > > Hi, > > just commit in some install clarify for pylons dependency, > > Besides the unittest, I think it's really a good chance to provide API > docs that we've been asked for years :p > > Anyone has a idea about API generation? > > > -- > Fred > > > > > -- 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 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 -~----------~----~----~----~------~----~------~--~---
