Documentation for REQUIRED_FIELDS on custom users is ambiguous
The documentation for the REQUIRED_FIELDS definition on a custom user model describes what fields must be included in required fields. It includes a note that says that USERNAME_FIELD should not be included in REQUIRED_FIELDS.
However, it doesn't say anything about password - which is a required field, and would otherwise meet the requirements of the REQUIRED_FIELDS definition. The note should be expanded (and the general definition clarified) to specifically exclude password.
This doesn't actually cause any problems -- it just means that the createsuperuser command asks for the password three times, instead of two, but it is confusing behaviour.
Change History
(7)
Triage Stage: |
Unreviewed → Accepted
|
Has patch: |
set
|
Needs documentation: |
unset
|
Owner: |
set to Tim Graham <timograham@…>
|
Resolution: |
→ fixed
|
Status: |
new → closed
|
FYI - this was reported by 项楠 on the users mailing list.