#21397: forms.TypedChoiceField validation problem
---------------------------------+------------------------------------
Reporter: Elec | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 1.6
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by claudep):
* severity: Normal => Release blocker
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => Bug
* stage: Unreviewed => Accepted
Comment:
This was changed in [9883551d50e].
Interesting use case, which is currently not tested in Django. Having the
coerced value not in choices is a bit of a corner case (and not clearly
documented), but I admit this might be considered as a regression.
I'll see if I can come up with a fix which is not too invasive...
In any case, the documentation will have to be clarified on this point.
--
Ticket URL: <https://code.djangoproject.com/ticket/21397#comment:1>
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/062.9ffa37db1aa3d5930c8ec9297bbdbbd1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
