#19412: Document that custom user models require a `user_permissions` M2M
---------------------------------+--------------------------------------
Reporter: cdestigter | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.5-beta-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
user_permissions is only required if you try to check permissions on the
user object, and that should only happen if you port over the permission
check methods from AbstractUser.
However, the relationship between the ModelBackend and permissions
definitely deserves to be documented.
There may also be some crossover here with a request from django-dev to
abstract out the AbstractUser permissions bits into a mixin model that can
be re-used.
--
Ticket URL: <https://code.djangoproject.com/ticket/19412#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
