#30216: Document BooleanField is no longer blank=True in Django 2.1+
--------------------------------------+------------------------------------
Reporter: Ed Morley | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 2.1
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):
* type: Uncategorized => Cleanup/optimization
* easy: 1 => 0
* stage: Unreviewed => Accepted
Comment:
I'm not sure what the note would say exactly. Is
"`BooleanField.__init__()` no longer sets `blank=True`." enough? It
doesn't seem to give much explanation about possible ramifications of the
change and it's not Django's place to describe how django-rest-framework
is affected. This behavior isn't documented in `ref/models/fields.txt`,
and we normally don't include a versionchanged annotation for something
that's undocumented.
--
Ticket URL: <https://code.djangoproject.com/ticket/30216#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 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/066.4fb858f83c206f319943d7afe2f157de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
