From a92cc84b4a206d18a5f1a0eaa47f19add40ff99b Mon Sep 17 00:00:00 2001 From: Tim Schilling Date: Mon, 30 Mar 2020 21:16:33 -0500 Subject: Refs #31369 -- Deprecated models.NullBooleanField in favor of BooleanField(null=True). --- docs/ref/checks.txt | 2 ++ docs/ref/models/fields.txt | 7 +++++-- 2 files changed, 7 insertions(+), 2 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/checks.txt b/docs/ref/checks.txt index d9bfdb168c..d9b56c3c58 100644 --- a/docs/ref/checks.txt +++ b/docs/ref/checks.txt @@ -202,6 +202,8 @@ Model fields in historical migrations. * **fields.W902**: ``FloatRangeField`` is deprecated and will be removed in Django 3.1. *This check appeared in Django 2.2 and 3.0*. +* **fields.W903**: ``NullBooleanField`` is deprecated. Support for it (except + in historical migrations) will be removed in Django 4.0. File fields ~~~~~~~~~~~ diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index cbc3b6142c..19750eedc3 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1182,8 +1182,11 @@ values are stored as null. .. class:: NullBooleanField(**options) -Like :class:`BooleanField` with ``null=True``. Use that instead of this field -as it's likely to be deprecated in a future version of Django. +Like :class:`BooleanField` with ``null=True``. + +.. deprecated:: 3.1 + + ``NullBooleanField`` is deprecated in favor of ``BooleanField(null=True)``. ``PositiveBigIntegerField`` --------------------------- -- cgit v1.3