#14705: Model Field Order not influenced by MRO of superclasses
------------------------------------------+---------------------------------
Reporter: vanschelven | Owner: nobody
Status: new | Milestone: 1.3
Component: Core framework | Version: SVN
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
------------------------------------------+---------------------------------
Changes (by russellm):
* owner: russellm => nobody
Comment:
If we were talking about a critical component of Django, I might agree to
taking a "fix the problem, then fix the fix" approach. In fact, I did just
that with #9964 only days ago. However, I don't think this problem falls
into that category. Django has had model inheritance for a while, and this
is the first time this problem has been reported. It requires a complex
model inheritance structure and a reliance on automated form ordering
before it becomes a problem.
I'm sorry that deferring this will be inconvenient to you, but I'd ask you
to also consider *my* inconvenience -- the fact that landing a suboptimal
bugfix *increases* my work as a framework maintainer in the long run,
because at some point, I'll have to reconcile two disparate
representations of base classes.
Two issues of protocol:
* Backwards compatibility isn't strictly an issue here, because _meta
isn't stable API. There are certain aspects of _meta that I'd be very
pained to change (like the basic field management stuff that has been that
way since the beginning), but I don't think parents falls into that list.
* Please don't assign bugs to other people without their permission.
--
Ticket URL: <http://code.djangoproject.com/ticket/14705#comment:11>
Django <http://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.
