On 9/17/06, Matt Good <[EMAIL PROTECTED]> wrote:
>
> Elvelind Grandin wrote:
> > On 9/16/06, Matt Good <[EMAIL PROTECTED]> wrote:
> > >
> > > 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,
> >
> > No need for this. TG already depends on Paste.
>
> TG depends on PasteScript, not Paste. PasteScript is related to, but
> does not depend on Paste. It used by TG for the "quickstart"
> templates. In order to use tg.fancy_exception you need the
> EvalException middleware, which is included in the Paste package.
I know what in TG uses PasteScript, I wrote the code ;)
But PasteScript does depend on Paste. So TG by default will have
evalExeption installed.
> -- Matt Good
>
>
> >
>
--
cheers
elvelind grandin
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
