Django: How to ensure the function name and context name are the same for context processing

[elfs]

We frequently write little functions that populate the Django context, and sometimes we want that context to be site-wide, and we want every page and every Ajax handler, basically everything that takes a request and spews a response, in our application to have access to that information.  It might the user’s authentication, or his authorization, or

Comments

[tamino]

I wonder what the performance characteristics of that are, versus something like:

def context_processor(f):
name = f.__name__
return lambda request: {name: f(request)}

@context_processor
def need_browser_warning(request):
return not adequate_browser(request.META.get('HTTP_USER_AGENT'))

[elfs]

The inspect method is significantly faster. Invoking the two with the profile active shows that the indirection of the decorator doubles run-time commitment.