Commit 6a30f5a2 authored by Malcolm Tredinnick's avatar Malcolm Tredinnick
Browse files

[1.0.X] Fixed #7011 -- Clarified what User.is_active really means in the documentation.

Backport of r9176 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9179 bcc190cf-cafb-0310-a4f2-bffc1f526a37
parent 378dadc2
Loading
Loading
Loading
Loading
+9 −2
Original line number Diff line number Diff line
@@ -89,8 +89,15 @@ Fields

    .. attribute:: models.User.is_active

        Boolean. Designates whether this account can be used to log in. Set this
        flag to ``False`` instead of deleting accounts.
        Boolean. Designates whether this user account should be considered
        active. Set this flag to ``False`` instead of deleting accounts.

        This doesn't control whether or not the user can log in. Nothing in
        the authentication path checks the ``is_active`` flag, so if you want
        to reject a login based on ``is_active`` being ``False``, it is up to
        you to check that in your own login view. However, permission checking
        using the methods like :meth:`~models.User.has_perm` does check this
        flag and will always return ``False`` for inactive users.

    .. attribute:: models.User.is_superuser