Marek Baczynski, el domingo  8 de enero a las 12:24 me escribiste:
> Cliff Wells napisal(a):
> 
> > *Much* easier to track down.   I think a couple hours with grep
> > searching for exception blocks and adding some code to print/log/save
> > the traceback would go a long way to making debugging apps easier.  Of
> > course, if you do much more than printing the exception, great care must
> > be taken that *that* code doesn't raise an exception itself ;-)
> 
> When I was playing with Twisted and Nevow, I absolutely fell in love
> how good the exception reporting was. Tracebacks (when allowed) showed
> not only the whole exception stack, but also (IIRC) several lines of
> context, all that with pretty html formatting. Soooo nice.

They probably use cgitb[1] from standard python distribution. It could be
nice to integrate it to TG too...

[1] http://www.python.org/doc/2.4.2/lib/node471.html

-- 
Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/
 .------------------------------------------------------------------------,
  \  GPG: 5F5A8D05 // F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05 /
   '--------------------------------------------------------------------'
Es más probable que el tomate sea perita, a que la pera tomatito.
        -- Peperino Pómoro

Reply via email to