Author: SmileyChris
Date: 2011-01-14 02:31:14 -0600 (Fri, 14 Jan 2011)
New Revision: 15204

Modified:
   django/trunk/django/contrib/auth/__init__.py
   django/trunk/docs/releases/1.3.txt
   django/trunk/docs/topics/auth.txt
Log:
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.

Modified: django/trunk/django/contrib/auth/__init__.py
===================================================================
--- django/trunk/django/contrib/auth/__init__.py        2011-01-14 05:04:14 UTC 
(rev 15203)
+++ django/trunk/django/contrib/auth/__init__.py        2011-01-14 08:31:14 UTC 
(rev 15204)
@@ -33,7 +33,7 @@
 
     if not hasattr(cls, 'supports_inactive_user'):
         warn("Authentication backends without a `supports_inactive_user` 
attribute are deprecated. Please define it in %s." % cls,
-             DeprecationWarning)
+             PendingDeprecationWarning)
         cls.supports_inactive_user = False
     return cls()
 

Modified: django/trunk/docs/releases/1.3.txt
===================================================================
--- django/trunk/docs/releases/1.3.txt  2011-01-14 05:04:14 UTC (rev 15203)
+++ django/trunk/docs/releases/1.3.txt  2011-01-14 08:31:14 UTC (rev 15204)
@@ -151,7 +151,7 @@
 the response. The final output of the response is not computed until
 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.
 
 Caching changes
@@ -172,8 +172,8 @@
 Lastly, support for pylibmc_ has been added to the memcached cache
 backend.
 
-For more details, see the :ref:`documentation on
-caching in Django<topics/cache>`.
+For more details, see the :doc:`documentation on
+caching in Django</topics/cache>`.
 
 .. _pylibmc: http://sendapatch.se/projects/pylibmc/
 
@@ -183,7 +183,7 @@
 If you provide a custom auth backend with ``supports_inactive_user`` set to
 ``True``, an inactive user model will check the backend for permissions.
 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
 ~~~~~~~~~

Modified: django/trunk/docs/topics/auth.txt
===================================================================
--- django/trunk/docs/topics/auth.txt   2011-01-14 05:04:14 UTC (rev 15203)
+++ django/trunk/docs/topics/auth.txt   2011-01-14 08:31:14 UTC (rev 15204)
@@ -1644,7 +1644,7 @@
 
 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
-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.
 
 The support for anonymous users in the permission system allows for

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to