[Zope] how to print error stack trace

[Michel Pelletier]

> -----Original Message-----
> From: Martijn Pieters [mailto:mj@antraciet.nl]
> Sent: Thursday, September 09, 1999 10:16 AM
> To: Evan Simpson; Jay, Dylan
> Cc: zope@zope.org
> Subject: Re: [Zope] how to print error stack trace
> 
> 
> At 15:49 09/09/99 , Evan Simpson wrote:
> >Errors which occur before the URL is fully resolved, and the 
> resulting
> >object called, generate hardwired error pages.  Only after 
> that process is
> >complete is there an acquisition context in which 
> standard_error_html can be
> >found.
> >
> >I'm not sure if there's a better way to handle it.
> 
> Maybe use the context build up until the error occurs?
> 
> /a/b/c/*BANG*
> 
> use /a/b/c/standard_html_error
> 
> /a/b/c/d/*BANG*
> 
> use /a/b/c/d/standard_html_error..
> 

This is how it works now.

I think what Evan was pointing to is the pre-2.0 behavior of using
hardwired error pages for errors which happen before a context is even
entered, like 404 NotFound and 500 ServerError.

-Michel