#3235: resolve_variable performance issue raising VariableDoesNotExist
-----------------------------------------------+----------------------------
Reporter: Karen Tracey <[EMAIL PROTECTED]> | Owner: adrian
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Template system | Version:
Severity: normal | Keywords:
-----------------------------------------------+----------------------------
This has come up a couple of times on django-users: the raising of
VariableDoesNotExist in resolve_variable can potentially cause a big
performance hit since it may result in the entire template context being
stuffed into a string. See:
http://groups.google.com/group/django-
users/browse_thread/thread/60332a3ab2a14fb2/ed01f52525c9af02#ed01f52525c9af02
and
http://groups.google.com/group/django-
users/browse_thread/thread/82df8bb71571fdbf/35089038df9c1976
I'll attach a patch with (what I think is) Russ Magee's suggested fix of
simply including the type of object being searched instead of a full repr
of it.
--
Ticket URL: <http://code.djangoproject.com/ticket/3235>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
