I agree, why not always pass the single auth backend into the login function?
If the backend is inferred by a single value in the settings and not stored alongside the user ID, what would happen to existing users who are already logged in when a second backend is added to the settings and deployed? Django would no longer know which backend to use to fetch the authenticated user? Cheers. Tai. On Saturday, May 23, 2015 at 6:58:35 AM UTC+10, Unai Zalakain wrote: > > Hi Paulo! > > >If the application has only one backend we always infer it in the login > >function. If it isn't, the client needs to provide one explicitly. > > Why not pass the single auth backend into the login function? It makes > the design and the documentation much simpler. > > -- > unai > -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0319a35d-b870-4edd-8805-a2707a8b0f58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
