#23130: BooleanField should not override 'blank' if choices are specified
-------------------------------------+-------------------------------------
Reporter: Jonas H. | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: assigned => new
* owner: Lynn Cyrin => (none)
Comment:
I created #29227 for the issue of allowing `BooleanField` to be
`null=True`. The PR there is ready for review. I'll leave this ticket open
as I'm not sure if there's additional work to be done to resolve it. Even
if no further code changes are required, a test for this use case might be
added.
--
Ticket URL: <https://code.djangoproject.com/ticket/23130#comment:22>
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.13e9cf9f8b818c03dc4c0fbf126e1531%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
