diff options
Diffstat (limited to 'docs/topics/auth/customizing.txt')
| -rw-r--r-- | docs/topics/auth/customizing.txt | 20 |
1 files changed, 4 insertions, 16 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 8b4da2048e..01d52d9262 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -180,13 +180,10 @@ The permissions given to the user will be the superset of all permissions returned by all backends. That is, Django grants a permission to a user that any one backend grants. -.. versionadded:: 1.8 - - If a backend raises a :class:`~django.core.exceptions.PermissionDenied` - exception in :meth:`~django.contrib.auth.models.User.has_perm()` or - :meth:`~django.contrib.auth.models.User.has_module_perms()`, - the authorization will immediately fail and Django - won't check the backends that follow. +If a backend raises a :class:`~django.core.exceptions.PermissionDenied` +exception in :meth:`~django.contrib.auth.models.User.has_perm()` or +:meth:`~django.contrib.auth.models.User.has_module_perms()`, the authorization +will immediately fail and Django won't check the backends that follow. The simple backend above could implement permissions for the magic admin fairly simply:: @@ -494,11 +491,6 @@ Django expects your custom User model to meet some minimum requirements. what these two methods return - if you want, they can return exactly the same value. -.. versionchanged:: 1.8 - - Older versions of Django required your model to have an integer primary - key as well. - The easiest way to construct a compliant custom User model is to inherit from :class:`~django.contrib.auth.models.AbstractBaseUser`. :class:`~django.contrib.auth.models.AbstractBaseUser` provides the core @@ -526,8 +518,6 @@ password resets. You must then provide some key implementation details: ... USERNAME_FIELD = 'identifier' - .. versionadded:: 1.8 - :attr:`USERNAME_FIELD` now supports :class:`~django.db.models.ForeignKey`\s. Since there is no way to pass model instances during the :djadmin:`createsuperuser` prompt, expect the @@ -562,8 +552,6 @@ password resets. You must then provide some key implementation details: ``User`` model, but should *not* contain the ``USERNAME_FIELD`` or ``password`` as these fields will always be prompted for. - .. versionadded:: 1.8 - :attr:`REQUIRED_FIELDS` now supports :class:`~django.db.models.ForeignKey`\s. Since there is no way to pass model instances during the :djadmin:`createsuperuser` prompt, expect the |