#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: Ready for checkin | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
---------------------------------------------+------------------------------
Changes (by julien):
* stage: Accepted => Ready for checkin
Comment:
I've updated the patch so that it applies to trunk. I've also renamed the
'bases' attribute to 'model_bases' to avoid any confusion.
I'm RFC'ing this patch as I think it solves an annoying inconsistency.
I've just got one little reservation: possibly this will be backwards
incompatible for people who were relying on that inconsistency. Although I
don't think this is a big deal. I'll leave the core devs to make a call on
this.
--
Ticket URL: <http://code.djangoproject.com/ticket/14705#comment:8>
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.
