#24487: Need for some retrocompatibility guidance for devs, on new OrderedDict
usage
-------------------------------+--------------------------------------
Reporter: pakal | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.7
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by pakal):
These SortedDict methods were alas documented
(https://docs.djangoproject.com/en/1.6/ref/utils/#module-
django.utils.datastructures), that's why I fear a bunch of libs using
dynamic forms may have relied on them.
Nice to see this field ordering API, I guess it'll prevent hacks in most
cases.
Concerning the need to dynamically insert/remove the fields present in
v1.7 forms (I have some needs like this for complex forms, checking for
authentications at runtime), I'm not sure about the way to go, maybe using
declarative Forms is not suited for that, and it'd be better to
dynamically build form classes, than to rely on their __init__ operations
?
--
Ticket URL: <https://code.djangoproject.com/ticket/24487#comment:2>
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/063.bfc243ea482c096fd920d344cd96f879%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
