I'll agree that mod_python 3.3 tracebacks are perhaps longer than they
need to be given that I factored out various stuff into some functions
so as to be able to reuse it across connection, handler and filter dispatch.
I also like the idea of using colour to highlight important stuff.
Thus, probably a good time to upgrade the standard traceback page
that mod_python generates when there is an error. In others words,
incorporate your ideas into the CallBack.ReportError function in the
mod_python.apache module. When integrated, will have to be a bit
more tricky to deal with fact that could be any phase and handler name
for phase can be overridden. The information to do all that should be
available though.
I'll get it working for "regular" handlers, and if the others are
non-obvious I'll get help on this mailing list.
Anyone else got any other ideas of what to put in the page? For example,
perhaps stuff like what req.filename, req.path_info, req.uri etc are set to.
That kind of thing should go below the traceback, so as to prevent the
problem of having to scroll to see the error from being repeated. I
wonder if it would be useful to present a formatted dump of lots of
information in the req, server, connection objects.
Once we get a feel what would be good to see, I'll create a JIRA issue for
it and reference the discussion in the mailing list archive.
With all my talk of dependency graphs, am thinking I could also put that
code in mod_python.testhandler module so as to be optionally used by
people as an aid for debugging applications as well.
Yes, good idea.
-Dan
