Why does Zope move the Error Type and Value and replace with (see above)
Mark Poole wrote:
(Object: standard_html_header) KeyError: (see above)
A frequent complaint is that people don't include the error type and value when reporting errors from Zope, they just include the traceback. Now, normal python tracebacks include both the error type and error value. Why does Zope make this not happen? cheers, Chris
On Tue, 2002-10-08 at 11:53, Chris Withers wrote:
Mark Poole wrote:
(Object: standard_html_header) KeyError: (see above)
A frequent complaint is that people don't include the error type and value when reporting errors from Zope, they just include the traceback.
Now, normal python tracebacks include both the error type and error value. Why does Zope make this not happen?
This code, which is inaccessible for TTW scripts but interferes with TTW rendering nonetheless, is in lib/python/ZPublisher/HTTPResponse.py in 2 places around line 620. It blindly assumes the exception has already been mentioned in the template and replaces the exception in the traceback formatting routine with '(see above)'. It also bothers me no end, but I believe (but haven't checked) that's all changed in Zope 2.6 with the new exception logging system. Cheers, Leo -- Ideas don't stay in some minds very long because they don't like solitary confinement.
Shane, can you confirm this? cheers, Chris Leonardo Rochael Almeida wrote:
Now, normal python tracebacks include both the error type and error value. Why does Zope make this not happen?
This code, which is inaccessible for TTW scripts but interferes with TTW rendering nonetheless, is in lib/python/ZPublisher/HTTPResponse.py in 2 places around line 620. It blindly assumes the exception has already been mentioned in the template and replaces the exception in the traceback formatting routine with '(see above)'. It also bothers me no end, but I believe (but haven't checked) that's all changed in Zope 2.6 with the new exception logging system.
On Wed, 9 Oct 2002, Chris Withers wrote:
Shane, can you confirm this?
cheers,
Chris
I can confirm it has changed. Overall description here: http://dev.zope.org/Wikis/DevSite/Proposals/BetterTracebacks Shane
Leonardo Rochael Almeida wrote:
Now, normal python tracebacks include both the error type and error value. Why does Zope make this not happen?
This code, which is inaccessible for TTW scripts but interferes with TTW rendering nonetheless, is in lib/python/ZPublisher/HTTPResponse.py in 2 places around line 620. It blindly assumes the exception has already been mentioned in the template and replaces the exception in the traceback formatting routine with '(see above)'. It also bothers me no end, but I believe (but haven't checked) that's all changed in Zope 2.6 with the new exception logging system.
Shane Hathaway wrote:
I can confirm it has changed. Overall description here:
http://dev.zope.org/Wikis/DevSite/Proposals/BetterTracebacks
looks cool :-) Are there details of what did/didn't get done, how it was done, and end user documentation anywhere? cheers, Chris
On Wed, 9 Oct 2002, Chris Withers wrote:
Shane Hathaway wrote:
I can confirm it has changed. Overall description here:
http://dev.zope.org/Wikis/DevSite/Proposals/BetterTracebacks
looks cool :-)
Are there details of what did/didn't get done, how it was done, and end user documentation anywhere?
Everything got done. The wiki page has enough details on how it was done. The end-user documentation is in the Zope Book. (As Chris McDonough says, the Zope Book is now authoritative.) Shane
Shane Hathaway wrote:
Everything got done. The wiki page has enough details on how it was done. The end-user documentation is in the Zope Book. (As Chris McDonough says, the Zope Book is now authoritative.)
Cooooool :-) Chris
participants (3)
-
Chris Withers -
Leonardo Rochael Almeida -
Shane Hathaway