From 649118961ce3952138536235fc842921e39bfa33 Mon Sep 17 00:00:00 2001 From: Preston Holmes Date: Wed, 20 Feb 2013 15:32:35 -0800 Subject: [PATCH] Fixed #19868 -- Clarified purpose of custom user example --- docs/topics/auth/customizing.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 2e7bf2e3db..c5d9e4ff7b 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -904,7 +904,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::