#16291: Document that TypedChoiceField does not coerce empty_value
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
vanschelven | Status: new
Type: | Component: Documentation
Cleanup/optimization | Severity: Normal
Milestone: | Keywords:
Version: 1.3 | Has patch: 0
Resolution: | Needs tests: 0
Triage Stage: Accepted | Easy pickings: 1
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by julien):
* needs_better_patch: => 0
* component: Uncategorized => Documentation
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
Coercing `empty_value` would be backwards-incompatible. Also, it is better
practice and more pythonic for the developer to explicitly provide an
already correctly-typed empty value if they wish to customise the `coerce`
function. So it is a matter of clarifying the documentation to explain the
current behaviour.
--
Ticket URL: <https://code.djangoproject.com/ticket/16291#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 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 this group at
http://groups.google.com/group/django-updates?hl=en.
