#29386: Meta Inheritance for default_permissions
-------------------------------+--------------------------------------
Reporter: Clayton Daley | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
This is expected behaviour.
The [https://docs.djangoproject.com/en/2.0/topics/db/models/#proxy-models
Proxy models docs] say:
> Proxy models inherit Meta attributes in the same way as regular models.
Here they link to the
[https://docs.djangoproject.com/en/2.0/topics/db/models/#meta-and-multi-
table-inheritance Meta and and multi-table inheritance section] which
says:
> ... it doesn’t make sense for a child class to inherit from its parent’s
Meta class... However, there are a few limited cases where the child
inherits behavior from the parent: if the child does not specify an
`ordering` attribute or a `get_latest_by attribute`, it will inherit these
from its parent.
`default_permissions` is not amongst the listed exceptions, so there is no
reason to expect it would be inherited.
--
Ticket URL: <https://code.djangoproject.com/ticket/29386#comment:2>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.6c80c62e222d33a260b4283ead6fa592%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
