#14705: Model Field Order not influenced by MRO of superclasses
------------------------------------------+---------------------------------
Reporter: vanschelven | Owner: russellm
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 ambv):
* owner: nobody => russellm
Comment:
The reason I introduced `model_bases` instead of rearranging half the
framework around changes in `parents` was to keep the patch minimal (e.g.
easier to get right). On top of that, I believe in backwards compatibility
and I'm not sure if there isn't some 3rd party code using `parents` in
ways that could have been broken by changing that.
I am willing to help with any refactoring of Meta necessary. However, this
is naturally milestone 1.4, e.g. over 9 months away. Could you please
reassess whether we could integrate the patch as it is? Without that
change I will need to basically fork Django until another stable release.
This is not easy to monkey patch.
--
Ticket URL: <http://code.djangoproject.com/ticket/14705#comment:10>
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.
