#21224: TypedChoiceField does not properly coerce 'None' in certain
circumstances
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.5
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* status: new => closed
* resolution: => worksforme
Comment:
That change:
https://github.com/django/django/commit/1123f4551158b7fc65d3bd88c375a4517dcd0720
#diff-aee6730bae795d31efec3c5d014804a9R511
...should solve your issue, as the `None` choice will be rendered as the
empty string in the option value, then coercion should consider it as the
empty value. Reopen if you can reproduce an issue with master code.
--
Ticket URL: <https://code.djangoproject.com/ticket/21224#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/067.a68bfbce87d9976c49f4a02db2cf034d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
