Hi. I have 'issues' with Contexts, RequestContexts and templatetags. Possibly this is my problem and not Django's, but I'd like to be persuaded of that.
I want to get the user in a templatetag, which seems like a perfectly reasonable and common thing to want to do. As far as I can tell the way to do this is to modify *every* *view* *in* *my* *project* to pass either the user or a RequestContext. This removes the possibility of decoupling the app with the templatetag in it, and seems generally a bit unsanitary. An obvious upstream solution would be to provide a way (if there isn't one already) to basically replace Context() with RequestContext() project-wide. I'm not sure if the devs envisage this kind of 'global' use of RequestContexts or if they're supposed to be more exceptional - if it's the former than I guess this would be an OK solution. Nirvana would seem to me to be the ability to specify context processors for the templatetag that don't pollute other contexts, and allow for proper decoupling. I imagine that would be fairly notty to implement, but hopefully there are people reading that know better than I do... So, can anyone tell me anything that'll make me happier about all of this? Am I missing something obvious? Cheers, Joe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
