summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2021-01-13 21:28:09 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2021-01-14 17:50:04 +0100
commitd992f4e3c29a81c956d3d616f0bc19701431b26e (patch)
tree3eebb321ef640126a8a1ad6c9f6273a73dc57463 /docs
parent06eec3197009b88e3a633128bbcbd76eea0b46ff (diff)
Refs #31369 -- Removed models.NullBooleanField per deprecation timeline.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/checks.txt5
-rw-r--r--docs/ref/models/fields.txt11
-rw-r--r--docs/releases/2.1.txt4
-rw-r--r--docs/releases/4.0.txt3
-rw-r--r--docs/topics/forms/modelforms.txt2
5 files changed, 9 insertions, 16 deletions
diff --git a/docs/ref/checks.txt b/docs/ref/checks.txt
index 48ffb8c816..e79a50b831 100644
--- a/docs/ref/checks.txt
+++ b/docs/ref/checks.txt
@@ -206,7 +206,10 @@ Model fields
* **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.
+ in historical migrations) will be removed in Django 4.0. *This check appeared
+ in Django 3.1 and 3.2*.
+* **fields.E903**: ``NullBooleanField`` is removed except for support in
+ historical migrations.
* **fields.W904**: ``django.contrib.postgres.fields.JSONField`` is deprecated.
Support for it (except in historical migrations) will be removed in Django
4.0.
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 3409d2d023..aedf115e08 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -1254,17 +1254,6 @@ To query ``JSONField`` in the database, see :ref:`querying-jsonfield`.
objects and arrays (represented in Python using :py:class:`dict` and
:py:class:`list`) are supported.
-``NullBooleanField``
---------------------
-
-.. class:: NullBooleanField(**options)
-
-Like :class:`BooleanField` with ``null=True``.
-
-.. deprecated:: 3.1
-
- ``NullBooleanField`` is deprecated in favor of ``BooleanField(null=True)``.
-
``PositiveBigIntegerField``
---------------------------
diff --git a/docs/releases/2.1.txt b/docs/releases/2.1.txt
index 21e9388680..bc03a67dce 100644
--- a/docs/releases/2.1.txt
+++ b/docs/releases/2.1.txt
@@ -189,8 +189,8 @@ Models
now support using field transforms.
* :class:`~django.db.models.BooleanField` can now be ``null=True``. This is
- encouraged instead of :class:`~django.db.models.NullBooleanField`, which will
- likely be deprecated in the future.
+ encouraged instead of ``NullBooleanField``, which will likely be deprecated
+ in the future.
* The new :meth:`.QuerySet.explain` method displays the database's execution
plan of a queryset's query.
diff --git a/docs/releases/4.0.txt b/docs/releases/4.0.txt
index d3bb700aac..4e89cf2230 100644
--- a/docs/releases/4.0.txt
+++ b/docs/releases/4.0.txt
@@ -305,3 +305,6 @@ to remove usage of these features.
* The ``list`` message for ``ModelMultipleChoiceField`` is removed.
* Support for passing raw column aliases to ``QuerySet.order_by()`` is removed.
+
+* The ``NullBooleanField`` model field is removed, except for support in
+ historical migrations.
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt
index 586b668da9..179762474a 100644
--- a/docs/topics/forms/modelforms.txt
+++ b/docs/topics/forms/modelforms.txt
@@ -106,8 +106,6 @@ Model field Form field
:class:`ManyToManyField` :class:`~django.forms.ModelMultipleChoiceField`
(see below)
-:class:`NullBooleanField` :class:`~django.forms.NullBooleanField`
-
:class:`PositiveBigIntegerField` :class:`~django.forms.IntegerField`
:class:`PositiveIntegerField` :class:`~django.forms.IntegerField`