On 4/24/06, Jeff Marshall <[EMAIL PROTECTED]> wrote: > One issue I hit when developing the API with TG is the "500 Server > Error" that it kicks back to developers when non-utf-8 characters are > passed in (since I've got the decodingFilter enabled with utf-8) or > when they don't pass in all of the required arguments. For the second > case, I feel like I need to switch all of my API methods to (*args, > **kw) and then do some validation myself in order to return a more > useful error code. I'm not sure what to do about generating a more > useful error for the decoding filter case. (Note: this is released on > TG 0.8.9, so if there's something in the 0.9 line for this already then > I apologize).
TG 0.9 no longer raises an exception if there are extra parameters. I would think that if a parameter is required, that *is* an error of some kind. Error handling is dramatically improved in 0.9/1.0. (BTW, the decoding filter is on by default in 0.9.) Is the problem the error message that's displayed? Those are exceptional conditions and it seems like *some* error should be shown. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
