Hi, Did you try writing a patch? I naively tried "class MultiValueDict(OrderedDict):" as the only change and it doesn't pass the tests. Perhaps more adaptations are required.
As for the motivation, I'm not sure if you described the problem in enough detail. (i.e. what does "It makes highly dynamic form situations more tedious to handle" mean?) If Python 3.6 preserves order, is this only an issue on Python 3.5? If so, I'd guess there would be little motivation in making a change (if it's a non-trivial change) given 3.5 will be end-of-life soon enough (2020). On Friday, January 5, 2018 at 10:07:41 AM UTC-5, Ole Laursen wrote: > > Hi! > > Would it be possible to derive QueryDict (i.e. MultiValueDict) from an > OrderedDict instead of dict? > > I'm finding it increasingly irritating that the original order is kept by > the whole stack right until Django puts it into a dict. It makes some > highly dynamic form situations more tedious to handle. > > Now that Python 3.6 preserves the order of dicts as an implementation > detail, there should not be any performance overhead as far as I'm aware. > > > Ole > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/493aede0-5a74-4a22-aebf-c00a29f02cf5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
