Comments on: Django: How to ensure the function name and context name are the same for context processing http://www.elfsternberg.com/2009/09/17/django-how-to-ensure-the-function-name-and-context-name-are-the-same-for-context-processing/ Done, and gets things smart. Fri, 03 Feb 2012 14:39:41 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Elf Sternberg http://www.elfsternberg.com/2009/09/17/django-how-to-ensure-the-function-name-and-context-name-are-the-same-for-context-processing/comment-page-1/#comment-714 Elf Sternberg Thu, 17 Sep 2009 21:21:14 +0000 http://www.elfsternberg.com/?p=408#comment-714 That's true, but oddly enough, it's actually less performant. I ran the numbers, and the inspect method is twice as efficient under cProfile. Not that that's a good excuse for obfuscation, but it's a point in inspect's favor. That’s true, but oddly enough, it’s actually less performant. I ran the numbers, and the inspect method is twice as efficient under cProfile. Not that that’s a good excuse for obfuscation, but it’s a point in inspect’s favor.

]]> By: Leo Shklovskii http://www.elfsternberg.com/2009/09/17/django-how-to-ensure-the-function-name-and-context-name-are-the-same-for-context-processing/comment-page-1/#comment-713 Leo Shklovskii Thu, 17 Sep 2009 20:43:39 +0000 http://www.elfsternberg.com/?p=408#comment-713 ugh, and the comment form killed all of my spacing... should still be pretty clear :-/ ugh, and the comment form killed all of my spacing… should still be pretty clear :-/

]]> By: Leo Shklovskii http://www.elfsternberg.com/2009/09/17/django-how-to-ensure-the-function-name-and-context-name-are-the-same-for-context-processing/comment-page-1/#comment-712 Leo Shklovskii Thu, 17 Sep 2009 20:43:08 +0000 http://www.elfsternberg.com/?p=408#comment-712 This is a nifty idea, but you can do it in a slightly less sickly clever way if you were to put it in a decorator, for example: def same_name_in_context(fn): def new_func(*args): return { fn.func_name : fn(*args) } return new_func @same_name_in_context def need_browser_warning(request): return not adequate_browser(request.META.get('HTTP_USER_AGENT')) This is a nifty idea, but you can do it in a slightly less sickly clever way if you were to put it in a decorator, for example:

def same_name_in_context(fn):
def new_func(*args):
return { fn.func_name : fn(*args) }
return new_func

@same_name_in_context
def need_browser_warning(request):
return not adequate_browser(request.META.get(‘HTTP_USER_AGENT’))

]]>