Simon Belak <[EMAIL PROTECTED]> writes: > If neither of these conditions are met, error handling is taken to a lower > layer. For this to be consistent we would need to raise something along the > lines of NotImplementedError in case of 2). > > The only down-side to this aproach is a marginal boilerplate when using very > simple error handling schemes (e.g. where one uses validators purely for > conversions). > > Thoughts, suggestions?
I prefer the most clear solution: every method should have a decorator saying that it wants its errors to be handled elsewhere. This decorator receives the name of where errors should be sent to and all available information. If there's no decorator on a method and an error happens, then let it go through the normal path and either go to the browser screen or be handled by some other component. If there could be two handlers (one for form validation and another for exceptions), this would be great and make the logic easier to code something specific for each application. -- Jorge Godoy <[EMAIL PROTECTED]>
