Hi. @Andrew: I'll look at your post anon, as it's longer.
On Wednesday, 17 January 2018 20:46:27 UTC+1, Mehmet Dogan wrote: > > Can you give an example of what you mean by option 3. > Well, I don't a concrete suggestion in mind, but the general idea would be to have ModelBackend proxy to another class (a Strategy ?) that did the actual permission check. We'd then have (at least) two versions: one with the current implementation, and one with the alternative. Exactly how the user would configure which version to use (etc) would need thinking about. The question is whether it's worth the price of admission, vs just, say, subclassing ModelBackend. C. -- 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/fc4b4544-dd15-4672-8a5b-27e9bcb7d4a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
