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="skip@mojam.com" 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 (skip@mojam.com) http://www.mojam.com/ http://www.musi-cal.com/
I would love it if I could set some debug environment variable, run with -D="skip@mojam.com" 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.
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 (skip@mojam.com) http://www.mojam.com/ http://www.musi-cal.com/
Skip Montanaro wrote:
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.
Why not just use all of Zope and be done with it? cheers, Chris
Chris> Why not just use all of Zope and be done with it? That's *much* easier said than done as far as I can tell. I am maintaining long-lived web site (> five years old), which is a mixture of flat html files, CGI scripts, ZServer-published methods and XML-RPC. On the middle end, we use an XML-RPC server to support Perl, Python and Java clients. On the backend we just recently switched to MySQL from a homegrown database system. While most of these bits are supported by Zope, it would be a major undertaking to replace all of what we have with Zope at this point. I just don't have the time or energy sufficient to do this. Added to that, my business partners out on the left coast (the Mojam half of my signature) use Mason (our CTO was one of the original Mason developers), so any major reimplementation of Musi-Cal will use Mason, simply so we can have a common development platform for our web sites and I can get out of the web site maintenance business altogether. Note that most of the inertia has absolutely nothing to do with Zope's qualities. Mostly it has to do with the realities of doing business in a small dot com. I actually do use Zope proper for another non-work-related web site. -- Skip Montanaro (skip@mojam.com) http://www.mojam.com/ http://www.musi-cal.com/
Skip Montanaro wrote:
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).
Yeah, and in production mode it sticks it after the end of your </html> ...which I'm sure is bad. Does anyone know how to hack this off? Why is it there anyway? I'm sure it exposes some information you really don't want h4x0r5 to have about your software setup... cheers, Chris
participants (3)
-
Chris Withers -
John Chandler -
Skip Montanaro