From e5090a3b2abadeea9f300269055e723d26f9918b Mon Sep 17 00:00:00 2001 From: Carl Meyer Date: Fri, 16 Sep 2011 10:53:15 +0000 Subject: [PATCH] Fixed #16094 -- Added missing colon in custom permissions docs. git-svn-id: http://code.djangoproject.com/svn/django/trunk@16836 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/auth.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt index 285406eafc..6dcf5488ab 100644 --- a/docs/topics/auth.txt +++ b/docs/topics/auth.txt @@ -1394,7 +1394,7 @@ The only thing this does is create those extra permissions when you run value of these permissions when an user is trying to access the functionality provided by the application (viewing tasks, changing the status of tasks, closing tasks.) Continuing the above example, the following checks if a user may -view tasks: +view tasks:: user.has_perm('app.view_task') @@ -1753,4 +1753,4 @@ Handling object permissions Django's permission framework has a foundation for object permissions, though there is no implementation for it in the core. That means that checking for object permissions will always return ``False`` or an empty list (depending on -the check performed). \ No newline at end of file +the check performed).