On Mon, Oct 27, 2008 at 8:59 PM, bo <[EMAIL PROTECTED]> wrote: > thus i do not need > django.core.context_processors.auth) but "contrib.admin" screams if it > is not included.
I don't want to steer the thread off-topic, but I've been bitten by this as well. My specific usecase is a project in which I subclass User and would prefer to populate 'user' in the context with my own subclass, but doing that would entail giving up the admin. It's ultimately a problem of contrib.admin wanting a context processor when I think it could just as easily be done by having contrib.admin pass the context explicitly - wanting 'djagno.core.context_processors.auth' is *not* a universal thing (per this thread - it causes an eager DB hit), and it seems odd that admin would require it. Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
