#35767: Don't recommend using a custom user model when starting a new project
-------------------------------------+-------------------------------------
Reporter: Carlton Gibson | Owner: Carlton
Type: | Gibson
Cleanup/optimization | Status: closed
Component: Documentation | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
No, I think there was keenness to move the steps there to a proper _How
To_. I have no problem with that at all.
The (minimal) goal here was simply to remove the impression (to new users,
stumbling upon it) that (with hyperbole, but that's how it get
interpreted) there's some need for tearing down your project and starting
again if you didn't use a custom user model.
As per the diff on the PR, a small tweak was all that was entailed.
I've written at length elsewhere my wider views, which are pretty
conservative. I'm not out to shake up the world.
--
Ticket URL: <https://code.djangoproject.com/ticket/35767#comment:11>
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/01070192a0b28f85-008b364c-50e4-490a-9be7-5597d9856dca-000000%40eu-central-1.amazonses.com.
