#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 Tim Graham):

 For the record, I think it's premature to remove the recommendation and
 tone down the warning, given all the chaos in #25313. Unless the plan is
 to deprecate `AUTH_MODEL_USER`...

 For instance, comment:29:ticket:25313:

 > At the start of our first real Django project we anticipated needing
 authentication eventually, so followed instructions from
 ​https://docs.djangoproject.com/en/4.0/topics/auth/customizing
 /#customizing-authentication-in-django. (we expected to use an email
 address instead of username for the identification token). We basically
 stubbed it until we knew what we needed. For our 2nd project we thought we
 would never need authentication so did nothing relating to users. We are
 now likely to nuke our databases and rebuild to avoid the migration
 complications described in this ticket.
 >
 > Given the impact of customizing authentication mid-project, why doesn't
 the default setup simply create an appropriate stub? Is the problem
 choosing an appropriate stub? Maybe that's easier than solving migration?

 I just closed #27909 (Use AUTH_USER_MODEL in startproject template) as
 wontfix since it contradicts the change in this ticket.

 One week since the initial forum post seems kind of fast to conclude a
 long-standing discussion about this topic.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35767#comment:8>
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/010701920034544c-e7bb36e7-f113-4d65-bff3-9fdd32ba1c3a-000000%40eu-central-1.amazonses.com.

Reply via email to