Re: [Zope3-dev] Re: Correction to RFC
Tres Seaver wrote: Thought so! I'm just not sure whether this is intended behaviour. What's the current policy about displaying tracebacks to the end-user in Zope 3? The policy seems to be that the end user should *never* see the traceback, unless she selects the '++skin++Debug' skin *and* the admin configures inclusion of the 'zope.app.debug' package. Personally, I think this is a mistake. The number of times the traceback screen dumped by an end user and mailed to me in a word doc has significantly aided fixing a hard to reproduce error is not insignificant... ...mindyou, I still wish Zope 3 had an easier concept of a customsiable standard_error_message, but maybe I'm missing something :-S Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Correction to RFC
Chris Withers wrote: Tres Seaver wrote: Thought so! I'm just not sure whether this is intended behaviour. What's the current policy about displaying tracebacks to the end-user in Zope 3? The policy seems to be that the end user should *never* see the traceback, unless she selects the '++skin++Debug' skin *and* the admin configures inclusion of the 'zope.app.debug' package. Personally, I think this is a mistake. The number of times the traceback screen dumped by an end user and mailed to me in a word doc has significantly aided fixing a hard to reproduce error is not insignificant... I would never want an end user to see a traceback. And I don't have a customer who would. Tracebacks can be logged. You could set up a logger that emailed all error log events to you, so you could see the error without your user seeing it. ...mindyou, I still wish Zope 3 had an easier concept of a customsiable standard_error_message, but maybe I'm missing something :-S Yes you are. In Zope 3, you can define an error view per error type, including a default view for Exception. This is wildly more flexible and easier to manage than in Zope 2. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Correction to RFC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Theune wrote: On Fri, 2006-01-27 at 16:38 -0700, Shane Hathaway wrote: It's checked in, but perhaps there is some other code that also needs to use the custom traceback formatter. The conversion is trivial. Replace this: from traceback import print_exception print_exception(...) with this: from zope.exceptions.exceptionformatter import print_exception print_exception(...) Thought so! I'm just not sure whether this is intended behaviour. What's the current policy about displaying tracebacks to the end-user in Zope 3? The policy seems to be that the end user should *never* see the traceback, unless she selects the '++skin++Debug' skin *and* the admin configures inclusion of the 'zope.app.debug' package. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD2/lF+gerLs4ltQ4RAqVpAJ408lAfr/qAgr8RXHQufyCleNTZiQCeKWgX OrpMsZSxywRiYDMGh77WjXM= =EGCT -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
