#32791: Documentation unclear on custom user models
-------------------------------------+-------------------------------------
Reporter: Matthew Somerville | Owner: Nishant
| Sagar
Type: Uncategorized | Status: closed
Component: Documentation | Version: 3.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: assigned => closed
* resolution: => needsinfo
Comment:
Hi Matthew — thanks for the report.
I have to say we need to go back to the DevelopersMailingList for this.
There are as many opinions as there are developers: ranging from "use the
default model, or you end up using your auth model as a random data bin"
to "we should update the default template to create the subclass, so users
don't find this advise until too late" to ... — if we could agress the
canonical advice then a rewrite might be on the cards.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/32791#comment:2>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.8477899be42172d949e1eeef0fe59190%40djangoproject.com.
