#29386: Meta Inheritance for default_permissions
-------------------------------------+-------------------------------------
Reporter: Clayton Daley | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
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 Carlton Gibson):
Replying to [comment:4 Clayton Daley]:
> The section you cited says "child class to inherit from its parent’s
Meta class" ...
Those words go " it doesn’t make sense for a child class to inherit from
its parent’s Meta class". Don't you think the "it doesn't make sense" is
clear enough?
It follows "All the Meta options have already been applied to the parent
class and applying them again would normally only lead to contradictory
behavior".
What else do you want it to say?
--
Ticket URL: <https://code.djangoproject.com/ticket/29386#comment:5>
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.0b6a6d55008c39746471b49a7af465d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
