Re: [Zope] What options exist for dealing with tracebacks?
John> Although Didier Georgieff has given a thorough reply, I couldn't John> resist a quick plug... ;-) John> http://www.zope.org/Members/JohnC/StandardErrorMessage John> which has info on using and customising error pages, including John> e-mailing of errors. Thanks, interesting, but in my case, probably not immediately useful. It slipped my mind when posting that I need to qualify all my zope posts with, "I'm not using full-blown Zope. I only use ZServer + DocumentTemplates." Still, knowing that there is some mechanism for Zope doing this, gives me hope that I can perhaps do it just by twiddling bits in my code. -- Skip Montanaro ([EMAIL PROTECTED]) http://www.mojam.com/ http://www.musi-cal.com/ ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] What options exist for dealing with tracebacks?
> I would love it if I could set some debug environment variable, run with > -D="[EMAIL PROTECTED]" or subclass some Error class and have tracebacks > mailed > to me. I wouldn't even care about the flood of email. At least I'd > have > all the inputs. Although Didier Georgieff has given a thorough reply, I couldn't resist a quick plug... ;-) http://www.zope.org/Members/JohnC/StandardErrorMessage which has info on using and customising error pages, including e-mailing of errors. Hope that's also of interest. John -- John Chandler / Software Developer / New Information Paradigms Ltd [ Linux in the office, AmigaOS in the home, PalmOS in the pocket ] The opinions above aren't those of my company... ...but then, they aren't really mine either. ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
[Zope] What options exist for dealing with tracebacks?
Having only recently upgraded from Zope 2.0 to 2.2.1 I see that the default behavior for traceback reporting is still to embed them in an HTML comment (or display them when debugging). Are there other options for dealing with tracebacks? I'm just using ZServer to publish my own modules. I'm not using all of Zope. My users don't know Python from HTML from a hole-in-the-wall. Asking them to root around in HTML source or cut-n-paste tracebacks is a no-win situation. Besides, to ask them to do that I suspect I'd have to fiddle the Zope source code directly. I would love it if I could set some debug environment variable, run with -D="[EMAIL PROTECTED]" or subclass some Error class and have tracebacks mailed to me. I wouldn't even care about the flood of email. At least I'd have all the inputs. Thx, -- Skip Montanaro ([EMAIL PROTECTED]) http://www.mojam.com/ http://www.musi-cal.com/ ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
