[Django] #27909: Use AUTH_USER_MODEL in quick-start template
Django
-----------------------------------------+------------------------
Reporter: David D Lowe | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
The documentation says:
https://docs.djangoproject.com/en/1.10/topics/auth/customizing/#using-a
-custom-user-model-when-starting-a-project
> If you’re starting a new project, it’s highly recommended to set up a
custom user model, even if the default User model is sufficient for you.
This model behaves identically to the default user model, but you’ll be
able to customize it in the future if the need arises:
If you fail to remember to do this when you set up the project, the
documentation warns of the difficulty of doing it later:
> Changing AUTH_USER_MODEL after you’ve created database tables is
significantly more difficult since it affects foreign keys and many-to-
many relationships, for example.
> This change can’t be done automatically and requires manually fixing
your schema, moving your data from the old user table, and possibly
manually reapplying some migrations. See #25313 for an outline of the
steps.
And it continues, explaining the other difficulties and caveats.
Starting your project with AUTH_USER_MODEL set is highly recommended, and
it is a difficult to switch to this method once a project has been
created. So why doesn't the default template created by `django-admin
startproject` give a value to `AUTH_USER_MODEL` by default?
--
Ticket URL: <https://code.djangoproject.com/ticket/27909>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: David D Lowe | Owner: nobody
Cleanup/optimization |
Component: Core (Management | Version: 1.10
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Someday/Maybe
* component: Uncategorized => Core (Management commands)
Comment:
This was proposed in ticket:24370#comment:3, however, it should be
discussed on the DevelopersMailingList to ensure there's consensus about
it. Feel free to start a thread.
--
Ticket URL: <https://code.djangoproject.com/ticket/27909#comment:1>
Django
-------------------------------------+-------------------------------------
Cleanup/optimization |
Component: Core (Management | Version: 1.10
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Tobias Kunze):
Since you need a model to hand to AUTH_USER_MODEL, and this model should
be in an app, you can't really populate this setting in `startproject`,
before having run `startapp`. Adding an app directly on `startproject`
seems like taking the defaults too far, at least to me, so I'm not clear
on where this value for AUTH_USER_MODEL is supposed to come in.
--
Ticket URL: <https://code.djangoproject.com/ticket/27909#comment:2>
Django
-------------------------------------+-------------------------------------
Cleanup/optimization |
Component: Core (Management | Version: 1.10
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by David D Lowe):
I guess the underlying issue is that it is so hard to migrate from not
having AUTH_USER_MODEL set to having it set. If it were easier to migrate,
then it wouldn't matter what it was set to in the startproject template.
--
Ticket URL: <https://code.djangoproject.com/ticket/27909#comment:3>
Django
-------------------------------------+-------------------------------------
Cleanup/optimization |
Component: Core (Management | Version: 1.10
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Timothy Allen):
I've issued a PR that does this and makes the configuration directory
named `config` instead of `{{ project_name }}` here:
https://github.com/django/django/pull/15609
These two items have been the most frequent pain points I've run into when
teaching newcomers.
--
Ticket URL: <https://code.djangoproject.com/ticket/27909#comment:4>
Django
-------------------------------------+-------------------------------------
Cleanup/optimization |
Component: Core (Management | Version: 1.10
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Carsten Fuchs):
* cc: Carsten Fuchs (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/27909#comment:5>
Django
-------------------------------------+-------------------------------------
Cleanup/optimization |
Component: Core (Management | Version: 1.10
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Thibaud Colas):
👋 reading this ticket, and https://forum.djangoproject.com/t/django-new-
project-structure-name/9987/10, and https://groups.google.com/g/django-
developers/c/SwFAy8GbhmE – it seems to me like this is only blocked by the
decision on the project structure. Other than that blocker, I see lots of
approval for:
- A custom user model by default
- It being in a `users` app
- And there’s been no feedback on Tim’s PR to name said model `User` in a
`models.py` file (phew).
I thought I’d record this here to note at least what there seems to be
consensus on.
--
Ticket URL: <https://code.djangoproject.com/ticket/27909#comment:6>
Django
-------------------------------------+-------------------------------------
Cleanup/optimization |
Component: Core (Management | Version: 1.10
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tom Carrick):
* cc: Tom Carrick (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/27909#comment:7>
Django
-------------------------------------+-------------------------------------
Component: Core (Management | Version: 1.10
commands) |
Keywords: | Triage Stage:
| Someday/Maybe
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* status: new => closed
Comment:
This seems obsolete as of #35767, since it's no longer recommended to
start a project with a custom user model.
--
Ticket URL: <https://code.djangoproject.com/ticket/27909#comment:8>