[Grok-dev] better error messages
sebastian at urbantalk.se
Sat May 10 06:52:11 EDT 2008
9 maj 2008 kl. 15.19 skrev Peter Bengtsson:
>>> (2) Therefore, if we detect an error and can simply print out "you
>>> have a Foo view in app.py but no foo.pt template", then we
>>> should; a traceback into Grok's correctly-working (!) code that
>>> it executed to produce the error is irrelevant. Heck, even if
>>> it *is* a bug in Grok that caused the message, the traceback is
>>> probably irrelevant, since the bit grokking logic that went
>>> wrong is probably long done by then! :-)
> In fact I think there are plenty other errors that could be
> "grokified" to better help junior developers (aka. "django users").
> Especially nasty are those that aren't pythonic where the last 20
> lines the traceback is about something in a ZCML file.
I have had quite a number of those questions in the past... :) Let me
know if you want a listing of cases that I have run into.
More information about the Grok-dev