innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Change the lack of supports_inactive_user on an auth backend to a 

!PendingDeprecationWarning (refs #14249), fixing some bad links in the
1.3 release docs and a typo.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15204 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Chris Beaven 2011-01-14 08:31:14 +00:00
parent 92d4352283
commit faa4a98f27
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
django/contrib/auth/__init__.py
View File

@ -33,7 +33,7 @@ def load_backend(path):
if not hasattr(cls, 'supports_inactive_user'): if not hasattr(cls, 'supports_inactive_user'):
warn("Authentication backends without a `supports_inactive_user` attribute are deprecated. Please define it in %s." % cls, warn("Authentication backends without a `supports_inactive_user` attribute are deprecated. Please define it in %s." % cls,
DeprecationWarning) PendingDeprecationWarning)
cls.supports_inactive_user = False cls.supports_inactive_user = False
return cls() return cls()

8
docs/releases/1.3.txt
View File

@ -151,7 +151,7 @@ of the template and context that was provided by the view to compute
the response. The final output of the response is not computed until the response. The final output of the response is not computed until
it is needed, later in the response process. it is needed, later in the response process.
For more details, see the :ref:`documentation </ref/template-response>` For more details, see the :doc:`documentation </ref/template-response>`
on the :class:`~django.template.TemplateResponse` class. on the :class:`~django.template.TemplateResponse` class.
Caching changes Caching changes
@ -172,8 +172,8 @@ prefixing <cache_key_prefixing>` and :ref:`transformation
Lastly, support for pylibmc_ has been added to the memcached cache Lastly, support for pylibmc_ has been added to the memcached cache
backend. backend.
For more details, see the :ref:`documentation on For more details, see the :doc:`documentation on
caching in Django<topics/cache>`. caching in Django</topics/cache>`.
.. _pylibmc: http://sendapatch.se/projects/pylibmc/ .. _pylibmc: http://sendapatch.se/projects/pylibmc/
@ -183,7 +183,7 @@ Permissions for inactive users
If you provide a custom auth backend with ``supports_inactive_user`` set to If you provide a custom auth backend with ``supports_inactive_user`` set to
``True``, an inactive user model will check the backend for permissions. ``True``, an inactive user model will check the backend for permissions.
This is useful for further centralizing the permission handling. See the This is useful for further centralizing the permission handling. See the
:ref:`authentication docs <topics-auth>` for more details. :doc:`authentication docs </topics/auth>` for more details.
GeoDjango GeoDjango
~~~~~~~~~ ~~~~~~~~~

2
docs/topics/auth.txt
View File

@ -1644,7 +1644,7 @@ Authorization for inactive users
An inactive user is a one that is authenticated but has its attribute An inactive user is a one that is authenticated but has its attribute
``is_active`` set to ``False``. However this does not mean they are not ``is_active`` set to ``False``. However this does not mean they are not
authrozied to do anything. For example they are allowed to activate their authorized to do anything. For example they are allowed to activate their
account. account.
The support for anonymous users in the permission system allows for The support for anonymous users in the permission system allows for