[Grok-dev] grok reference - what needs to be documented and what not

[Lennart Regebro]

On 5/29/07, Jan-Wijbrand Kolman <janwijbrand at gmail.com> wrote:
> You have to keep in mind though, this *is* a *reference*. This implies
> completeness to me. The reference actually starts out with saying it
> should not be read as an introduction or tutorial to Grok.

Well, the Python library reference i also not an introduction or
tutorial, but still only mentions the classes and methods that you are
supposed to *use* and not any internals. Makes sense to me.

-- 
Lennart Regebro: Zope and Plone consulting.
http://www.colliberty.com/
+33 661 58 14 64