On Sep 19, 2010, at 7:01 PM, Chris McDonough wrote: > My $.02.. if you don't have a threadlocal tmpl_context around for > people to jam values onto/into, it'd just confuse people if the dict > values they returned from a view weren't passed as top-level names to > the template, and instead were made available as the subkey > "tmpl_context".
Well, there is a tmpl_context created on the request, that is available in templates as well. So it is around, created per-request as in Pylons 1.0, for ppl to add things to. So it might seem like a disconnect when someone add's things to tmpl_context in one case, but then it gets dropped in as a template global under the 'renderer=' scenario. Having everything a person wants to pass in, always go in under tmpl_context seems more consistent. - Ben -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
