#29386: Meta Inheritance for default_permissions
-------------------------------------+-------------------------------------
Reporter: Clayton Daley | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
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
-------------------------------------+-------------------------------------
Comment (by Clayton Daley):
Thanks. I finally see the chain of references that would have brought me
to that conclusion. It sounds like Meta Inheritance is supported under
few, very specific conditions... something like:
- A is the parent of B
- A.Meta is the parent of B.Meta
- A.Meta is abstract
If a concise set of conditions could be described, would you be open to a
PR that threw `ImproperlyConfigured` under other conditions? This seems
like an ideal case for an exception because Meta Inheritance is a best
practice in some cases (i.e. abstract inheritance) and deliberately
ineffective in others (Multi-Table, Proxy). A reasonably informative
error message would eliminate the need to even go to the documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/29386#comment:8>
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.33370359dfe74ce9a87eac20f11a55ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
