For the background to this problem please see my Stack Overflow
question here [1].
I recently had to do some head-scratching over Django 1.3's logging
configuration, because with DEBUG=True the 'django.request' logger
isn't called when an uncaught exception occurs during a request.
It wasn't obvi
On Mon, Jun 13, 2011 at 9:53 PM, Vinay Sajip wrote:
> On Jun 10, 2:05 pm, Matt Bennett wrote:
>
>> Is there a reason the call to logger.error can't come before we return
>> the technical_500_response when DEBUG=True? It seems to me that the
>> debug level should
> This is a case for a custom Filter object [1]. The filter object
> implementation would only be a few lines, to reject logging when DEBUG
> is True, and can be attached to the admin email handler in the default
> logging configuration. [2] This way the logging call can occur in all
> code paths,
On Fri, Jun 17, 2011 at 6:45 PM, Vinay Sajip wrote:
> Matt Bennett writes:
>
>>
>> > This is a case for a custom Filter object [1]. The filter object
>> > implementation would only be a few lines, to reject logging when DEBUG
>> > is True, and can be att
