[Grok-dev] rookie Grokker notes

Vincent Fretin vincent.fretin at gmail.com
Fri Feb 26 03:29:24 EST 2010

On Fri, Feb 26, 2010 at 6:28 AM, J. Cameron Cooper <jccooper at gmail.com> wrote:
> I'm a long-time Zope/Plone guy, but I'm starting my first real project with
> Grok. I figured I'd publicly document problems I've had getting started;
> hopefully they can be fixed and avoided, and at least they'd be
> discoverable. I'm not exactly a naive user, but I do have fresh eyes, so
> probably I can be of some help streamlining new developer startup.
> Item 1: getting a traceback for errors.
> Default config is to show a simple "system error" message. Unlike Zope 2,
> tracebacks are not shown on the console, nor--so far as I can tell--in the
> logs. (I'm not entirely certain about the Grok logging system, so tell me if
> I'm wrong; but, none of the log files extant had anything.)
> You can get a TTW traceback if running the debug.ini. This is, however, not
> easy. Requires a config change and a re-buildout. Also, it still doesn't go
> to the console or logs.

What about
bin/paster serve parts/etc/debug.ini

I actually never used myroject-debug and myproject-ctl in the newest
grok buildout. :)


More information about the Grok-dev mailing list