#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):
Hey Tim.
Thanks for closing the issue. Yes… I can see that line. I argued at length
why I don't agree, but I'd suggest that the 8 years that #27909 was
unresolved is exactly indication that the problems I've diagnosed are
real. Numerous attempts to progress the tutorial and start project
template have come to nothing because a sensible work around for the
custom user model problem couldn't be found. There comes a point where we
have to say enough is enough: this discussion has been stagnant for
essentially an age. I put forward a very minimal change to move us from
the impasse. I was somewhat surprised how positive the response was, but
it's only on the basis of that response that I opened the ticket.
> Unless the plan is to deprecate AUTH_MODEL_USER...
We so far away from actually removing it that I don't know how to sensibly
think about that. My suggestion is that we fix the complaints about
auth.User — login by email being the main one — and then custom users
models should just fade away. I can't see it being something to **remove**
though.
To be honest, I find the quoted comment misleading and alarmist. Migrating
isn't **that** hard, even if you're convinced it's necessary (which of
course I'm going to say it's not, right). The suggestion from the
community is to document those steps. I think that's a good idea.
I don't want to repeat everything I've written elsewhere, but I'm really
happy to chat with you about this. I value your opinion. I've argued that
auth is the ''leaky battery''. I don't think the issues with auth.User are
insurmountable. Imagine if we actually addressed them. What a much better
story we could tell. I don't know if you agree with any of what I said,
but I'd love to have your input pushing forward here.
--
Ticket URL: <https://code.djangoproject.com/ticket/35767#comment:9>
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/0107019200737c30-7c05d7e1-0808-4577-9449-6e5942e125fc-000000%40eu-central-1.amazonses.com.
