From: Dan Fairs <dan.fa...@gmail.com>
Date: Fri, 26 Feb 2010 13:28:41 +0000
Local: Fri, Feb 26 2010 8:28 am
Subject: Re: PISTON_DISPLAY_ERRORS and transaction handling
> Not sure what to do about this. Maybe warn if PISTON_DISPLAY_ERRORS is That'd help. > on together with the transaction middleware? Of course, it's not just the transaction middleware affected by this: it's any middleware that has a process_exception() method. Another possibility therefore might be to have Piston itself invoke process_exception() for all installed middlewares before returning the server error response, mimicking: django/handlers/base.py:97,101 for middleware_method in self._exception_middleware: I haven't investigated far enough to figure out if there would be any other problems with doing that. I do agree there's also an issue with Django too. I'll post a message on django-users to see what the feeling is about it there. Cheers, -- You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||