#23314: Docs should stay consistent and only recommend custom users for custom
authentication and authorization, not profile data
-------------------------------+--------------------
Reporter: gavinwahl | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version:
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The docs mostly recommend using the profile pattern for profile data and
only using a custom user for custom authentication and authorization:
<https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-
the-existing-user-model>
<https://docs.djangoproject.com/en/dev/topics/auth/customizing/#specifying-a
-custom-user-model>
However, this paragraph is consistent:
<https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-
django-s-default-user>
It should recommend using a OneToOneField for profile data, like the rest
of the docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/23314>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.e707c2c26c277944af40d9d6be5286f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
