Karl Guertin wrote: > On 9/15/06, Adam Jones <[EMAIL PROTECTED]> wrote: > > I am not familiar with Django's error reporting. Could you provide a > > link or description? > > You get a nicely formatted error page showing the line of code where > the error occured with a bit of context. The locals() at each level of > the stack are also available on the page. > > To answer the question, I believe the strategy will be a move to WSGI > in 1.1 where we can take advantage of Paste's (I think it's Paste) > error handling/reporting middleware.
This is already supported in TG 0.9/1.0. Install Paste so you have the EvalException middleware, then set "tg.fancy_exception" to True in your development config (obviously this should be turned off in production). In fact EvalException does much more than Django, since you can run Python code from the error page that's evaluated in one of the stack frames where the exception occurred. This is *very* useful for debugging, since simply looking at the repr() of the local variables often doesn't give you enough information. Of course improved WSGI support in 1.1 could allow easier use of other Paste middleware. I believe it provides one that will email exception information, which could be useful for production use. -- Matt Good --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
