#23130: BooleanField should not override 'blank' if choices are specified
-------------------------------------+-------------------------------------
Reporter: jonash | Owner: tushar
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by jonashaag):
Can't think of any documented/tested incompatibilities, except for
NullBooleanField being deprecated/superseded by BooleanField. But it may
have undocumented surprises, for instance for people who rely on the
behavior I consider a bug in my initial ticket description. Or for people
who expect the forced `blank=True` on BooleanFields.
--
Ticket URL: <https://code.djangoproject.com/ticket/23130#comment:16>
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/064.5418b7ff83497b18c4fede7eaa3d90f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
