Comments below, apologies for the email signature on previous emails! On Tue, Dec 20, 2011 at 7:56 PM, Paul McMillan <[email protected]> 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. > Agreed, this would be wrapped around get_traceback_html() most likely. > > > 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 think we should select some reasonable limits for these, and > hardcode them, rather than adding a setting. Users who are debugging > the entire contents of multi-megabyte variable values on the html > debug page are doing it wrong. > I completely agree. I'm wondering if it would be better to have the variable commented out with a small message if it's above X amount, or whether it should display up to X amount, then display a small message explaining why it's been clipped. > > -Paul > > -- > 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. > > -- 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.
