But each permission is uniquely defined on the model level as a tuple of
(content type, permission name). As content type refers to concrete model
within a concrete app, we should be using permission string of the format
"<app label>.<model name>.<permission codename>".
This becomes a concrete issue once one wants to define custom permissions
for their models, and doesn't observe the convention of putting the model
name in the permission codenames (or wants to inherit the custom
permissions form an abstract model).
See also https://groups.google.com/forum/#!searchin/django-
developers/permissions/django-developers/ngV5KhLXUrQ/DTfqhG0LRG4J .
--
Ticket URL: <https://code.djangoproject.com/ticket/25281>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_docs: => 0
* type: Bug => Cleanup/optimization
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
If someone wants to work on this, please add your implementation plan to
the mailing list thread to get feedback first.
--
Ticket URL: <https://code.djangoproject.com/ticket/25281#comment:1>
* owner: nobody => tsyplakou
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/25281#comment:2>
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/13086 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/25281#comment:3>
* needs_better_patch: 0 => 1
* needs_docs: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/25281#comment:4>
* owner: tsyplakou => (none)
* status: assigned => new
--
Ticket URL: <https://code.djangoproject.com/ticket/25281#comment:5>