On 5/15/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> In the very beginning, I often made trivial errors in some functions
> used by the methods. Sometimes this resulted in exceptions that were
> ignored and resulted in missing data. This is then hard to spot since
> you don't get a hint what e
Malcolm Tredinnick wrote:
> At some point we start to drown in config settings. It's probably better
> to just "Do The Right Thing" here (first, decide what the right thing
> should be). Having a way to always show the exception (if possible)
> seems like the right thing to me.
>
> The patch in
On 5/14/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> The patch in ticket #1852 looks like a good start. I was looking at it
> this morning and trying to trace through whether anything else needed
> similar modification. Not sure the output it produces is perfect, but it
> looks like a good
Hey Michael,
On Mon, 2006-05-15 at 05:30 +0200, Michael Radziej wrote:
> Hi,
>
> Django silently drops certain types of exceptions during exception
> processing.
>
> Now, while this is in general useful, it really obscures your bugs.
>
> I'd propose to optionally log those exceptions to st
Hi,
Django silently drops certain types of exceptions during exception
processing.
Now, while this is in general useful, it really obscures your bugs.
I'd propose to optionally log those exceptions to stdout when, say
settings.log_template_exceptions, is set.
What do you thing?
Michael
