#18431: TypedChoiceField doesn't use self.coerce in its clean() and
prepare_value()
methods
------------------------+--------------------------------------
Reporter: ambv | Owner: nobody
Type: Bug | Status: closed
Component: Forms | Version: 1.4
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
------------------------+--------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => invalid
Comment:
You're describing a very high level issue with the design of Django's
form. This doesn't lead to any clear, actionnable items. As a consequence
the ticket has languished here for five months without feedback.
I suggest taking this topic to the django-developers mailing list. You'll
reach a wider audience and it'll be a better medium for the discussion.
You should give more details; try to frame the problem and explain your
proposal.
If the discussion determines that Django's behavior should be changed —
taking into account backward-compatibility requirements — then you're
welcome to add details to this ticket and reopen it, or to open a new one.
--
Ticket URL: <https://code.djangoproject.com/ticket/18431#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
