From d3a8f36fdb3094e58db24065bc77ec790b95c789 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 11 May 2015 09:10:30 -0400 Subject: [PATCH] [1.8.x] Fixed #24780 -- Removed outdated discussion of signals and custom users. Backport of 8e86d9d3dfd68bebbfd1dd5006e0c25696855269 from master --- docs/topics/auth/customizing.txt | 9 --------- 1 file changed, 9 deletions(-) diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 954366b6d20..899959d9bc3 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -895,15 +895,6 @@ If your project uses proxy models, you must either modify the proxy to extend the User model that is currently in use in your project, or merge your proxy's behavior into your User subclass. -Custom users and signals ------------------------- - -Another limitation of custom User models is that you can't use -:func:`django.contrib.auth.get_user_model()` as the sender or target of a signal -handler. Instead, you must register the handler with the resulting User model. -See :doc:`/topics/signals` for more information on registering and sending -signals. - Custom users and testing/fixtures ---------------------------------