On Thursday 16 March 2017 02:29:21 guettli wrote: > In our custom code we already skip check1 and do only check2.
Why do you even do these checks? There's a view decorator and class-based view mixin. All you need to do is make good groups and users and the rest follows. If you want to define a new permission type, you can do it in the model meta class. Not one place requires manual permission checks - when you stick to the model level. If you need to enforce permissions at the model instance level, then don't reinvent the wheel. There's a few packages out there, who have already solved the problem - Django Guardian being one of them. -- Melvyn Sopacua -- You received this message because you are subscribed to the Google Groups "Django users" 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-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2070883.gQ4bCuiexO%40devstation. For more options, visit https://groups.google.com/d/optout.
