#10512: Ordering of non-model fields in a ModelForm, after #8164
-------------------------------+--------------------------------------------
Reporter: mbi | Owner: Alex
Status: closed | Milestone:
Component: Forms | Version: SVN
Resolution: fixed | Keywords: modelform, field order
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
-------------------------------+--------------------------------------------
Comment (by Alex):
Yes it does, the behavior of the SortedDict is that on update it doesn't
reset the position of the key. So basically what happens is it tries to
get a non Model field, it doesn't find it, it puts a None in the
fields_dict, then later that gets updated which keeps that key position.
And the tests demonstrate this.
--
Ticket URL: <http://code.djangoproject.com/ticket/10512#comment:9>
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
