#31369: Deprecate NullBooleanField
-------------------------------------+-------------------------------------
Reporter: David | Owner: nobody
Smith |
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: 3.0
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
#29227 allowed `BooleanField` to be null=true, a step towards deprecating
`NullBooleanField`. #27917 also mentions an aim to deprecate this field.
[https://github.com/django/django/pull/8467#discussion_r175504425
Comments] on the PR discussed deprecating `NullBooleanField` with the
conclusion being that we should wait a while. Now that we are almost 2
years on, and with Django 4.0 being sometime away I suggest now is a good
time to revisit this decision.
This ticket therefore proposes we deprecate `NullBooleanField`. It would
be good to also tidy up the associated fields / widgets e.g. #23681
discussed deprecation of `NullBooleanSelect`
Note: I was slightly unsure if this is best raised as a ticket or as a
topic on the mailing list.
--
Ticket URL: <https://code.djangoproject.com/ticket/31369>
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/051.3d60b6e91d67cd2db88bcdc1a66073b5%40djangoproject.com.
