On Wed, Mar 11, 2009 at 9:38 AM, Robert Neville <[email protected]> wrote: > When I went searching, I came to the conclusion that 2.0 has no such > decorator anymore. To be honest, I've only worked in 2.0 so I'm not even > clear what @exception_handler used to do, I just thought it might solve a > problem I was having when I was searching through the documentation.... > Yes I believe it was removed (At least I haven't seen it in the new code, and it uses generic-dispatch, which was (almost) removed entirely from the core) to reduce the amount of magic/bloat. If you have a case that could only be solved with it could be put up for discussion.
> If my assumption about what it does is correct, wouldn't it be clearer to > just enclose your code in a try...except block in your controller method and > redirect to the appropriate handler or is that not what @exception_handler > was for? here are the docs on it, but you are probably right, maybe the "more than source error same error" feature is worth it http://docs.turbogears.org/1.0/ErrorReporting > > On Wed, Mar 11, 2009 at 4:24 AM, Sanjay <[email protected]> wrote: >> >> Hi All, >> >> Could not find how to handle exceptions in TG 2.0, i.e. substitute of >> @exception_handler. Need help. >> >> thanks, >> Sanjay >> >> >> > > > > -- > Rob Neville > http://www.robneville.net > > http://www.linkedin.com/in/robneville > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
