> > > After some some thoughts, i figured out that one route to change how permissions work in Django can be done by changing AUTHENTICATION_BACKENDS to a Custom ModelBackend Subclass that query for Permissions in a different way or from a different model / Table; And this solution can be implemented by each developer in their project if they dislike how the current permission work or it is simply not enough for them.
So maybe we can be satisfied with the current Permission implementation for some more time. Hopefully this idea -customizing permissions by changing the ModelBackend Authentication , leaving the current Permission as it is- might come in handy if anyone is not satisfied with the Django Permissions . It can also be stated *more clearly* in the docs. Greetings to you all. -- 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 post to this group, send email to django-developers@googlegroups.com. 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/d69c8163-b57e-4771-b7c0-d66ffbe7faa2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
