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 debug page somewhat tedious to use. Temporarily, I've put a try/catch on MemoryError to generate a text based email, which at least tells us what originally happened, albeit with the useful variable information. With all this in mind, I would like to see if anyone else thinks the following might be a good idea - Place a try/catch for MemoryError on the exception handler to send back a simple exception traceback to the browser. - Include a configuration settings option to limit the maximum payload it will send back to the browser per variable (i.e. maybe 500kb per stack frame, or 2kb per variable etc) I'd be happy to provide a patch for this, assuming it has any chance of getting into the core. Any thoughts/feedback would be appreciated. Cal -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
