[Zope-Coders] Re: [Zope] Reclaim the Stupid Logfile Traceback Format!

[Guido van Rossum]

> <taking this back onto the lists to find out what the story is>
> 
> Johan Carlsson [EasyPublisher] wrote:
> > At 18:21 2002-12-05 +0000, Chris Withers said:
> > 
> >> Johan Carlsson [EasyPublisher] wrote:
> >>
> >>>>> Now I get file pointers in the Stupid Log File (not in the web 
> >>>>> traceback)
> >>>>
> >>>> What do you mean by 'file pointers'?
> >>>
> >>> Path + line number into the file where the error occurred.
> >>> I'm not really sure what to call them :-)
> >>
> >> Weird they only show up in the log file. Maybe ask on zope-coders 
> >> ayway to find out
> >> whether this is intentional or not. Seems a bit unhelpful to me...
> > 
> > I think it is intentional.
> 
> Well, Shane said it wasn't. I think it's a bad idea in any case. The
> format_exception in zLOG, unless I'm verymuch mistaken, should
> include the full traceback, which in 2.6.1b1 it doesn't :-(

Traditionally, the zLOG tracebacks have been formatted using the same
zope-specific traceback formatting code that is used for the HTML
tracebacks (but generating text format).  I found a problem with that,
because there are conditions where the zope-specific traceback
formatting code can invoke stuff left on the stack in magic variables
that is poisoned.  So I changed it to use a plain traceback from the
traceback module.  I think I only did this on thr trunk (i.e. Zope
2.7).  This isn't ideal either, because when it works, that magic
stuff is useful.

This is not the full story, I'm sure, but it is the only bit that I know.

--Guido van Rossum (home page: http://www.python.org/~guido/)