#31369: Deprecate NullBooleanField
-------------------------------------+-------------------------------------
Reporter: David Smith | Owner: hristiy4n
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: 3.0
(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
-------------------------------------+-------------------------------------
Comment (by hristiy4n):
"Deprecate NullBooleanField" is a bit of a broad naming. If I understand
correctly, for now just adding a "NullBooleanField has been deprecated."
message should be enough, and later on removing the field in favor of the
BooleanField.
{{{
system_check_deprecated_details = {
'msg': (
'NullBooleanField has been deprecated. Support '
'for it (except in historical migrations) will be removed '
'in Django 4.0.'
),
'hint': (
'Use BooleanField(null=true) instead.'
),
'id': 'fields.W903',
}
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31369#comment:6>
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.6e04909b151d32adbaaafe9c34259e18%40djangoproject.com.
