#20999: Cannot specify form_class that isn't subclass of TypedChoiceField for
field
with choices
-----------------------------+---------------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+---------------------------------------------
Comment (by carljm):
If this patch is not backported to 1.6, then the subclass check will be
released in 1.6 final, and not supporting it in 1.7 would be a backwards-
compatibility issue.
If others are ok with it, I'm happy to backport this fix to 1.6 now and
remove the subclass check entirely; that could potentially cause an issue
for someone upgrading from a 1.6 beta to 1.6 rc/final, but maybe that's
not a concern.
--
Ticket URL: <https://code.djangoproject.com/ticket/20999#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.1abb757216ace6d0bfc017dc7fa1ab50%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
