I personally am in favour of including this in Django at this point. It seems like a desirable feature, it has circulated the community since 2008 (!), and there are at least two community packages implementing the pattern. No one on this thread is explicitly against it ever happening.
I'm in favour of the approach of a second middleware rather than a setting for AuthenticationMiddleware. We do try to avoid settings and I think this is a more sensible approach. It would be relatively little code and documentation overhead - a middleware (maybe LoginRequiredAuthenticationMiddleware ?), a decorator (maybe @login_not_required ? - the opposite of @login_required), and a view mixin (LoginNotRequired ?). On Fri, 20 Mar 2020 at 18:25, Tobias Bengfort <tobias.bengf...@posteo.de> wrote: > Hi Mehmet, > > On 19/03/2020 09.49, Mehmet Ince wrote: > > To be honest, I’m kind a confused about how to proceed. Should I > > continue with settings to control it or subclass of Auth middleware ? > > Remember that many people on this mailing list (me included) are people > just like you, so we can only give you feedback and maybe some > additional ideas. > > The best course of action is probably to write a mail in which you sum > up the discussion so far, highlight some controversial points, and > describe why you decided the way you did in your implementation. At > least that is what I would do. > > The critical part in my experience is to convince people that this > should be included in django itself rather than a third party library. I > usually fail with that so I cannot say anything useful about that. > > tobias > > -- > 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 django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/469846ef-6d3a-c0c5-73d0-21b694185e81%40posteo.de > . > -- Adam -- 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 django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM2yHO3tP4FWHJGwVJsDGCtGm5D%3Dtua2h36agX5qtw01_Q%40mail.gmail.com.
