On Apr 10, 4:26 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > > It complicates the implementation, and, as you noted, slows down > slightly for all existing use cases of a callable. > > This isn't a problem in and of itself, except that the only benefit > you get for the complexity and slowdown is the ability to use > 'extra_context' instead of 'context_processor' in your generic view > declaration. I don't see this as benefit at all.
The complexity of those 3 lines will allow certain users (those not ready to look beyond generic views) to benefit while not impacting everyone else. It's more about the utility of 'extra_context' being limited because it lacks a request. It seems like an easy way to improve a convenience mechanism. I guess you can call that a benefit. > TEMPLATE_CONTEXT_PROCESSORS". It's easy to explain, and it provides a > neat excuse for introducing the idea of context processors, which have > uses outside the world of generic views. I also like to encourage people to learn and expand. It's nice to see. Thanks for your time and responses. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
