#30216: Document BooleanField is no longer blank=True in Django 2.1+
-------------------------------------+-------------------------------------
Reporter: Ed Morley | Owner: David Vaz
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 2.1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"1556a67c65c336ab12961c6123b129ac10e729b8" 1556a67c]:
{{{
#!CommitTicketReference repository=""
revision="1556a67c65c336ab12961c6123b129ac10e729b8"
[2.1.x] Fixed #30216 -- Doc'd that BooleanField is no longer blank=True in
Django 2.1.
Backport of a6972e88547ad5a51592f2b6d5046754c4b59394 from stable/2.2.x
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30216#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.353b3ae19e9d4d43e52d0d27d8ccaa41%40djangoproject.com.
