summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPreston Holmes <preston@ptone.com>2013-02-20 15:32:35 -0800
committerPreston Holmes <preston@ptone.com>2013-02-20 15:34:22 -0800
commitb17a572eb36acfa59cdf001c4ed3b965ade2b7a7 (patch)
treee9281443679bb32ae3acade12b7c05f50cda3bce
parent96790fc02214b4d36df0ecb630159e65b28a5174 (diff)
[1.5.x] Fixed #19868 -- Clarified purpose of custom user example
-rw-r--r--docs/topics/auth/customizing.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt
index fcda9c302e..a9193135e5 100644
--- a/docs/topics/auth/customizing.txt
+++ b/docs/topics/auth/customizing.txt
@@ -898,7 +898,9 @@ Here is an example of an admin-compliant custom user app. This user model uses
an email address as the username, and has a required date of birth; it
provides no permission checking, beyond a simple `admin` flag on the user
account. This model would be compatible with all the built-in auth forms and
-views, except for the User creation forms.
+views, except for the User creation forms. This example illustrates how most of
+the components work together, but is not intended to be copied directly into
+projects for production use.
This code would all live in a ``models.py`` file for a custom
authentication app::