Django

Code

Changeset 5774

Show
Ignore:
Timestamp:
07/29/07 13:21:16 (1 year ago)
Author:
adrian
Message:

Added 'New in Django development version' to changes in docs/authentication.txt from [5771]

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • django/trunk/docs/authentication.txt

    r5771 r5774  
    100100 
    101101    * ``is_authenticated()`` -- Always returns ``True``. This is a way to 
    102       tell if the user has been authenticated. This does not imply any  
     102      tell if the user has been authenticated. This does not imply any 
    103103      permissions, and doesn't check if the user is active - it only indicates 
    104104      that the user has provided a valid username and password. 
    …… 
    115115      password hashing in making the comparison.) 
    116116 
    117     * ``set_unusable_password()`` -- Marks the user as having no password set.  
    118       This isn't the same as having a blank string for a password. 
    119       ``check_password()`` for this user will never return ``True``. Doesn't  
    120       save the ``User`` object. 
    121        
    122       You may need this if authentication for your application takes place   
     117    * ``set_unusable_password()`` -- **New in Django development version.** 
     118      Marks the user as having no password set.  This isn't the same as having 
     119      a blank string for a password. ``check_password()`` for this user will 
     120      never return ``True``. Doesn't save the ``User`` object. 
     121 
     122      You may need this if authentication for your application takes place 
    123123      against an existing external source such as an LDAP directory. 
    124124 
    125     * ``has_usable_password()`` -- Returns ``False`` if  
    126       ``set_unusable_password()`` has been called for this user. 
     125    * ``has_usable_password()`` -- **New in Django development version.** 
     126      Returns ``False`` if ``set_unusable_password()`` has been called for this 
     127      user. 
    127128 
    128129    * ``get_group_permissions()`` -- Returns a list of permission strings that 
    …… 
    138139    * ``has_perms(perm_list)`` -- Returns ``True`` if the user has each of the 
    139140      specified permissions, where each perm is in the format 
    140       ``"package.codename"``. If the user is inactive, this method will  
     141      ``"package.codename"``. If the user is inactive, this method will 
    141142      always return ``False``. 
    142143 
    …… 
    164165The ``User`` model has a custom manager that has the following helper functions: 
    165166 
    166     * ``create_user(username, email, password=None)`` -- Creates, saves and  
     167    * ``create_user(username, email, password=None)`` -- Creates, saves and 
    167168      returns a ``User``. The ``username``, ``email`` and ``password`` are set 
    168169      as given, and the ``User`` gets ``is_active=True``. 
    169        
     170 
    170171      If no password is provided, ``set_unusable_password()`` will be called. 
    171172