From 1702be89c86d1b1a01efb16fa7836335ad709184 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 23 Feb 2013 15:42:56 -0500 Subject: [PATCH] [1.5.X] Fixed #19402 - Clarified purpose of CustomUser.REQUIRED_FIELDS Thanks pydanny for the report and ptone for the patch. Backport of 24a2bcbcdd from master --- docs/topics/auth/customizing.txt | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index a9193135e54..f974b5647dd 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -501,9 +501,16 @@ password resets. You must then provide some key implementation details: .. attribute:: REQUIRED_FIELDS - A list of the field names that *must* be provided when creating - a user. For example, here is the partial definition for a User model - that defines two required fields - a date of birth and height:: + A list of the field names that *must* be provided when creating a user + via the :djadmin:`createsuperuser` management command. The user will be + prompted to supply a value for each of these fields. It should include + any field for which :attr:`~django.db.models.Field.blank` is ``False`` + or undefined, but may include additional fields you want prompted for + when a user is created interactively. However, it will not work for + :class:`~django.db.models.ForeignKey` fields. + + For example, here is the partial definition for a ``User`` model that + defines two required fields - a date of birth and height:: class MyUser(AbstractBaseUser): ...