> the ModelBackend uses the Permission model, so why would that ever work without beeing in INSTALLED_APPS?
ModelBackend.authenticate() doesn't use the permissions models. And that's the method that gets used when authenticating a user. If I did something like `user.has_perm()`, things would blow up. But that is easy to override on your custom User class. > the context_processor will break due to the AnonymousUser most likely Hmm, right...I suppose AnonymousUser could be refactored into base_user.py. On Wednesday, March 23, 2016 at 3:39:57 PM UTC-7, Florian Apolloner wrote: > > > > On Wednesday, March 23, 2016 at 8:36:39 PM UTC+1, Matt wrote: >> >> I created https://code.djangoproject.com/ticket/26401 >> <https://www.google.com/url?q=https%3A%2F%2Fcode.djangoproject.com%2Fticket%2F26401&sa=D&sntz=1&usg=AFQjCNG7tek69HGtxC6RCZBQuW1ZQl5ZdA> >> >> > Since the usage of any of the backends requires models >> >> I used the ModelBackend with no issues in Django 1.8 (without auth in >> INSTALLED_APPS). So that is the place I want to refactor. >> > > Mhm, that would surprise me -- the ModelBackend uses the Permission model, > so why would that ever work without beeing in INSTALLED_APPS? And as for > the ticket you generated, the context_processor will break due to the > AnonymousUser most likely -- this is not backend related. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/717f643a-b6a0-4e53-aa23-118623bc255b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
