Yes, I can see the difficulties involved. However, the debugger being returned as the content that was requested when an error occurs is really just a convenience -- there's always the unique debug URL that is piped out to stdout as well.
I'd be perfectly satisfied if pylons/paste/etc were to simply abort the response if an error occurs, and leave me to figure out that I need to copy and paste the debug URL from the console to a new browser window. (Maybe also outputting some reasonable final content indicating that something went awry.) This behaviour would certainly need to be an .ini file option so as to not disturb expectations elsewhere (or, even better, add an attribute to the Response object so that each action could determine the appropriate behaviour, rather than having the setting apply application-wide). Chas Emerick Snowtide Informatics --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
