summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAymeric Augustin <aymeric.augustin@m4x.org>2014-03-10 21:11:23 +0100
committerAymeric Augustin <aymeric.augustin@m4x.org>2014-03-10 21:11:23 +0100
commit1be31c320c2e0efa1730f73509d64e024ab31a0c (patch)
tree9cca8ce13863e0249e4125a93d8b88216a70eda3 /docs
parentdaaf6cf9a4d2155d5fc59ab8bdcbbf328b523592 (diff)
Fixed #21875 -- Clarified that get_user_model() only works at run time.
Thanks Benjamin White for the report.
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.7.txt4
-rw-r--r--docs/topics/auth/customizing.txt4
2 files changed, 8 insertions, 0 deletions
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index 2dd3931060..934ad017c9 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -869,6 +869,10 @@ regressions cannot be ruled out. You may encounter the following exceptions:
will also trigger this exception. The ORM cannot function properly until all
models are available.
+ Another common culprit is :func:`django.contrib.auth.get_user_model()`. Use
+ the :setting:`AUTH_USER_MODEL` setting to reference the User model at import
+ time.
+
* ``ImportError: cannot import name ...`` This happens if the import sequence
ends up in a loop.
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt
index cc991cd951..55bd4811fd 100644
--- a/docs/topics/auth/customizing.txt
+++ b/docs/topics/auth/customizing.txt
@@ -426,6 +426,10 @@ different User model.
post_save.connect(post_save_receiver, sender=settings.AUTH_USER_MODEL)
+ Generally speaking, you should reference the User model with the
+ :setting:`AUTH_USER_MODEL` setting in code that is executed at import
+ time. ``get_user_model()`` only works once Django has imported all models.
+
Specifying a custom User model
------------------------------