[Grok-dev] better error messages

[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! :-)
>>
+1


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'll keep pushing for this as I go along if it's something we agree is
important. In other words, if I come across an error that could be
dumbed down or repackaged I'll propose a patch + tests.



-- 
Peter Bengtsson,
work www.fry-it.com
home www.peterbe.com
hobby www.issuetrackerproduct.com