On 12/31/06, Noah Gift <[EMAIL PROTECTED]> wrote:
Is there an elegant way to avoid nesting dictionaries in render_to_response if you have to separate data structures to display...from say another function that gets called in your view? The data structure I am displaying is already deeply nested, so I would like to avoid nesting even further if I can avoid it. It makes for a nasty template with too much nesting.
You can always subclass Context [1] and do your own thing - passing that in with the context_instance attribute, but even then, your custom context must return a dict. [1]: http://www.djangoproject.com/documentation/templates_python/#subclassing-context-requestcontext -- ---- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
