On 3/1/07, Tim Chase <[EMAIL PROTECTED]> wrote:
...
> the
> tracebacks seem to want to try and pull back some humongous
> portion of data (600k+ records in one table, and this is the
> "small" testing DB).
Those variables are somewhere in your call stack. The traceback
doesn't "want to" do it. It's unrolling the stack, and it works with
what it finds. :)
OTOH, it does sound reasonable to me to put some kind of safety valve
on the TB handling-- something no reasonable person would ever hit,
but might help you. ;-)
I think this is the bit that needs help:
django.views.debug.technical_500_response:
...
'vars': tb.tb_frame.f_locals.items(),
The problem is that this is all very generic code and there's no
telling what kind of object you're dealing with in the results of
.items().
(I wish Python had a convenient way to check the physical memory size
of an object graph.)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
