Question

My application is running on App Engine and is implemented using Werkzeug and Jinja2. I’d like to have something functionally equivalent of Django’s own context processor: a callable that takes a request and adds something to the template context. I already have a ‘context processors’ that add something to the template context, but how do I get this request part working? I implemented context processors as a callables that just return a dictionary that later is used to update context.

For example, I’d like to add something that is contained in request.environ.

Answer 1

One way of achieving this is through late-bound template globals using the thread-local proxy in Werkzeug.

A simple example that puts the request into the the template globals:

from werkzeug import Local, LocalManager local = Local() local_manager = LocalManager([local])  from jinja2 import Environment, FileSystemLoader  # Create a global dict using the local's proxy to the request attribute global_dict = {'request': local('request')} jinja2_env = Environment(loader=FileSystemLoader('/')) jinja2_env.globals.update(global_dict)  def application(environ, start_response):     '''A WSGI Application'''     # later, bind the actual attribute to the local object     local.request = request = Request(environ)      # continue to view handling code     # ...  application = local_manager.make_middleware(application) 

Now in any of your templates, the current request will appear bound to the variable ‘request’. Of course that could be anything else in environ. The trick is to use the local proxy, then set the value before you render any template.

I should probably also add that a framework like Glashammer (Werkzeug+Jinja2) streamlines this process for you by using events. Many functions can connect to the events during the process of the WSGI call (for example, when a request is created) and they can put stuff in the template namespace at that point.