From be12c9e9082c12e0510b88d08e735ea2af939b07 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Thu, 26 Apr 2012 17:15:40 +0000 Subject: Fixed #18038 -- Removed the 'supports_inactive_user' backwards-compatibility flag. Thanks Aymeric Augustin for the initial patch and Ramiro Morales for the review. git-svn-id: http://code.djangoproject.com/svn/django/trunk@17938 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/auth.txt | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) (limited to 'docs') diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt index 18f8947d87..8690b832e2 100644 --- a/docs/topics/auth.txt +++ b/docs/topics/auth.txt @@ -1831,8 +1831,6 @@ object the first time a user authenticates:: ADMIN_PASSWORD = 'sha1$4e987$afbcf42e21bd417fb71db8c66b321e9fc33051de' """ - supports_inactive_user = False - def authenticate(self, username=None, password=None): login_valid = (settings.ADMIN_LOGIN == username) pwd_valid = check_password(password, settings.ADMIN_PASSWORD) @@ -1931,15 +1929,8 @@ The support for anonymous users in the permission system allows for anonymous users to have permissions to do something while inactive authenticated users do not. -To enable this on your own backend, you must set the class attribute -``supports_inactive_user`` to ``True``. - -A nonexisting ``supports_inactive_user`` attribute will raise a -``PendingDeprecationWarning`` if used in Django 1.3. In Django 1.4, this -warning will be updated to a ``DeprecationWarning`` which will be displayed -loudly. Additionally ``supports_inactive_user`` will be set to ``False``. -Django 1.5 will assume that every backend supports inactive users being -passed to the authorization methods. +Do not forget to test for the ``is_active`` attribute of the user in your own +backend permission methods. Handling object permissions -- cgit v1.3