#11154: Inconsistency with permissions for proxy models
------------------------------+------------------------------------
Reporter: etianen | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: SVN
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by danny.adair@…):
Just wanted to add that etianen the ticket reporter is the author of
django-reversion and this inconsistency breaks real-life use cases, e.g.
https://github.com/etianen/django-reversion/issues/94
It may be a matter of discussion whether proxy models should have their
own permission or not (though I personally find that a no-brainer), but
really the issue is that two different vital locations report two
different "app_label" for the same class. I don't see a valid argument for
an explicitly specified "app_label" of a proxy model being reported as its
parent (root) model's "app_label".
--
Ticket URL: <https://code.djangoproject.com/ticket/11154#comment:32>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
