#3453: resolve_variable usage leads to redundant work
--------------------------------------------------+-------------------------
Reporter: Brian Harring <[EMAIL PROTECTED]> | Owner:
mtredinnick
Status: new | Component:
Template system
Version: SVN | Resolution:
Keywords: | Stage:
Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------------+-------------------------
Comment (by [EMAIL PROTECTED]):
@mtreddinick; any further thoughts on it?
I'll admit the backwards compatibility approach (resolve_variable
generating the instance, and invoking resolve) is kind of ugly, but don't
see any other alternatives.
--
Ticket URL: <http://code.djangoproject.com/ticket/3453#comment:3>
Django Code <http://code.djangoproject.com/>
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
-~----------~----~----~----~------~----~------~--~---
