From 58440c0b66cd3829a41fbe0ec791680cc4934175 Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Mon, 18 Jan 2010 20:51:29 +0000 Subject: [PATCH] Fixed typo in docs - supports_objects_permissions should be supports_object_permissions git-svn-id: http://code.djangoproject.com/svn/django/trunk@12256 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/auth.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt index 984d03c313..6707208283 100644 --- a/docs/topics/auth.txt +++ b/docs/topics/auth.txt @@ -1570,12 +1570,12 @@ the check performed). To enable object permissions in your own :ref:`authentication backend ` you'll just have to allow passing an ``obj`` parameter to the permission methods and set the -``supports_objects_permissions`` class attribute to ``True``. +``supports_object_permissions`` class attribute to ``True``. -A nonexistent ``supports_objects_permissions`` will raise a hidden +A nonexistent ``supports_object_permissions`` will raise a hidden ``PendingDeprecationWarning`` if used in Django 1.2. In Django 1.3, this warning will be upgraded to a ``DeprecationWarning``, which will be displayed -loudly. Additionally ``supports_objects_permissions`` will be set to ``False``. +loudly. Additionally ``supports_object_permissions`` will be set to ``False``. Django 1.4 will assume that every backend supports object permissions and -won't check for the existence of ``supports_objects_permissions``, which +won't check for the existence of ``supports_object_permissions``, which means not supporting ``obj`` as a parameter will raise a ``TypeError``.