test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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
This commit is contained in:
Carl Meyer 2011-09-16 10:53:15 +00:00
parent def775ae5e
commit e5090a3b2a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/topics/auth.txt
View File

@ -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 value of these permissions when an user is trying to access the functionality
provided by the application (viewing tasks, changing the status of tasks, provided by the application (viewing tasks, changing the status of tasks,
closing tasks.) Continuing the above example, the following checks if a user may closing tasks.) Continuing the above example, the following checks if a user may
view tasks: view tasks::
user.has_perm('app.view_task') user.has_perm('app.view_task')
@ -1753,4 +1753,4 @@ Handling object permissions
Django's permission framework has a foundation for object permissions, though 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 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 object permissions will always return ``False`` or an empty list (depending on
the check performed). the check performed).