On 12/17/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> James Bennett wrote:
> > This means the default implementation can happily use
> > django.contrib.auth and the existing is_staff flag and permission
> > system, but that using something else is as easy as subclassing and
> > overriding the right methods. And with a little refactoring to remove
> > the direct reliance on the LogEntry and Message models, it would be
> > easy to run the Django admin without django.contrib.auth
> When you say 'without django.contrib.auth' does it mean that one can
> ditch User model but still use django.contrib.auth to call custom
> AUTHENTICATION_BACKENDs, use it's context processor to populate {{ user }}?I don't want to speak for James, but that's how I see it. Joseph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
