From eba093e8b02989af1857b1915907ca0897f565ff Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 31 Dec 2016 11:46:40 -0500 Subject: Refs #25847 -- Removed support for User.is_(anonymous|authenticated) as methods. Per deprecation timeline. --- docs/topics/auth/customizing.txt | 10 ---------- 1 file changed, 10 deletions(-) (limited to 'docs/topics') diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index ff84fad19f..40675d2ef6 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -695,11 +695,6 @@ The following attributes and methods are available on any subclass of (representing the currently logged-in user), you should know this attribute is ``True`` for any :class:`~models.User` instance. - .. versionchanged:: 1.10 - - In older versions, this was a method. Backwards-compatibility - support for using it as a method will be removed in Django 2.0. - .. attribute:: models.AbstractBaseUser.is_anonymous Read-only attribute which is always ``False``. This is a way of @@ -707,11 +702,6 @@ The following attributes and methods are available on any subclass of objects. Generally, you should prefer using :attr:`~models.User.is_authenticated` to this attribute. - .. versionchanged:: 1.10 - - In older versions, this was a method. Backwards-compatibility - support for using it as a method will be removed in Django 2.0. - .. method:: models.AbstractBaseUser.set_password(raw_password) Sets the user's password to the given raw string, taking care of the -- cgit v1.3