On Wed, Nov 9, 2011 at 7:10 PM, Doug Ballance <dball...@gmail.com> wrote: > I very much like the idea of an optional keyword argument and > fallback. The template loader is one of the few places I've been > forced to use threadlocals to get get the job done. >
Please no - an optional argument is all well and good, until people start relying on that feature. Suddenly, you then have templates that are functionally tightly coupled to requests. I don't get why it is difficult to extract what you want from the request, place it in a context and render it. The OP's use case of wanting to modify the template used can be achieved either by calculating which template to use in the view, or by passing in the name of the template that should be extended as a variable when rendering. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
