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:
parent
def775ae5e
commit
e5090a3b2a
|
@ -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).
|
||||
the check performed).
|
||||
|
|
Loading…
Reference in New Issue