I'm planning a DocSprint for January 13th, the day before Bruce Eckel's TurboGears jam.
I'm still working on securing the space we need downtown, but I'm expecting that many of the contributers will only be available via skype, and other virtual means. The API docs need to be generated from docstrings, so somebody could work on the API doc generation process (I think Kevin has a plan for this) and others could work on improving our Docstring utilization. --Mark Ramm On 12/18/06, Steve Bergman <[EMAIL PROTECTED]> wrote: > > > OK. But I fear that "Indexed and Comprehensive API Docs" tops the > list. (A very tall order, I know!) > > How did "If it isn't documented, it doesn't exist" get left out of "The > Zen of Python"? > > Seriously. After much searching and uncertainty, I've decided on > Python as the language that I really want to devote time to learning > well. > > It's a beautiful language. I grok the philosophy. But for a language > that prizes explicitness, readability, maintainability, unit testing, > and great built in self-documentation features, it seems to me that > Python projects are particularly poorly documented. > > But I'm sure I can come up with a few things with a lower barrier to > entry than "A Complete API Reference" to submit to the wishlist. ;-) > > > > > -- 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" 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?hl=en -~----------~----~----~----~------~----~------~--~---
