#23314: Docs should stay consistent and only recommend custom users for custom
authentication and authorization, not profile data
--------------------------------------+------------------------------------
Reporter: gavinwahl | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version:
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"3569536491f16c9d112959d23cf3c18417063c54"]:
{{{
#!CommitTicketReference repository=""
revision="3569536491f16c9d112959d23cf3c18417063c54"
Fixed #23314 -- Tempered recommendation of storing profile data on custom
user.
Thanks gavinwahl for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23314#comment:3>
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/067.79c0b82a1eacb42dd9b8a0f6ec396c60%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
