#29918: Add support for checking object permissions in PermissionRequiredMixin ---------------------------------+------------------------------------ Reporter: Tobias Bengfort | Owner: nobody Type: New feature | Status: closed Component: contrib.auth | Version: 2.1 Severity: Normal | Resolution: wontfix Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 1 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 ---------------------------------+------------------------------------ Changes (by Carlton Gibson):
* status: new => closed * resolution: => wontfix Comment: As I [https://github.com/django/django/pull/10636#issuecomment-467902972 commented on the PR], I think that this code is much better off [https://github.com/django-guardian/django- guardian/blob/d3611494c1e40a67b20e32ffe9e5198a53923aa2/guardian/mixins.py#L56 remaining in django-guardian] rather than being copied into to django. The need only comes up when using an object permissions backend, which to all purposes just is django-guardian, so "use that" is IMO reasonable advice. I'm going to close as `wontfix` on that basis. -- Ticket URL: <https://code.djangoproject.com/ticket/29918#comment:7> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/060.7be20108cd3c6be7b95ae72fbccd0efe%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.