Comments below, apologies for the email signature on previous emails!
On Tue, Dec 20, 2011 at 7:56 PM, Paul McMillan wrote:
> > Place a try/catch for MemoryError on the exception handler to send back a
> > simple exception traceback to the browser.
>
> Yes, this makes sense, as long as we are su
Hi Alex,
Please note, I am already using a try/catch block on MemoryError, and this
does indeed resolve the problem.
I think at the very least, we should attempt to generate the text
exception, and if it fails due to a particular circumstance, then it will
just fall back to doing whatever it orig
On Tue, Dec 20, 2011 at 1:56 PM, Paul McMillan wrote:
> > Place a try/catch for MemoryError on the exception handler to send back a
> > simple exception traceback to the browser.
>
> Yes, this makes sense, as long as we are sure the memory error is
> raised by Django code, not user code.
>
> > In
> Place a try/catch for MemoryError on the exception handler to send back a
> simple exception traceback to the browser.
Yes, this makes sense, as long as we are sure the memory error is
raised by Django code, not user code.
> Include a configuration settings option to limit the maximum payload i
Hey,
So, we have a few clients who use Django for processing large amounts of
data in a single query.
If an exception is raised in development, the get_traceback_html() method
fails with a MemoryError, and in the event that it doesn't, you end up with
huge variable data print outs making the debu
