#23130: BooleanField should either forbid setting 'choices' or not override
'blank'
-------------------------------------+-------------------------------------
Reporter: jonash | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jonash):
Expected behavior when pressing "Save": The message "this field is
required" should appear, since it hasn't been filled out. This doesn't
work as expected because 'blank' is always set to True in the
BooleanField's `__init__` method. This is because a blank/absent value
means False if the BooleanField widget is a checkbox. But if rendered as a
choices list, things change. See initial description for a more elaborate
description of the issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/23130#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 [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/064.8fe38d5b0c0b17687f1077b0753da46d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
