#22740: Model gets Meta from abstract ancestor class in MTI
-------------------------------------+-------------------------------------
Reporter: Kronuz | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.6
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
Comment:
Your proposal would break code that relies on the currently documented
behaviour: https://docs.djangoproject.com/en/dev/topics/db/models/#meta-
inheritance
We can have a discussion on the django-developers mailing-list about the
advantages and drawbacks of inheriting Meta from abstract parents.
But we can't accept such a backwards-incompatible change without
discussion.
--
Ticket URL: <https://code.djangoproject.com/ticket/22740#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.ca0c2ded0bafc68ead7ac832accf6667%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
