#24487: Need for some retrocompatibility guidance for devs, on new OrderedDict
usage
-------------------------------+--------------------
Reporter: pakal | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The change from SortedDict to OrderedDict in django1.7 was not a drop-in
replacement, not only because several libs relied on the "hackish"
keyOrder to sort field, but also because the methods below have
disappeared, breaking libs (liek userprofile related stuffs) that made
good use of them :
{{{
insert(index, key, value)
Inserts the key, value pair before the item with the given index."
value_for_index(index)
Returns the value of the item at the given zero-based index.
}}}
Wouldn't it be helpful to add back these methods, in a subclass of
OrderedDict ? Or to provide some guidance on how people are supposed to
dynamically actiavte/deactivation form fields, now ?
It's unclear if completely replacing "myform.fields" with a new
ordereddict, to achieve this, might be harmful.
--
Ticket URL: <https://code.djangoproject.com/ticket/24487>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.05d5f2a9df46f66ad0648958bcca10ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
