#31369: Deprecate NullBooleanField
-------------------------------------+-------------------------------------
Reporter: David Smith | Owner: Hristiyan
Type: | Ivanov
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Timothy Schilling):
* cc: Timothy Schilling (added)
* has_patch: 0 => 1
Comment:
I [https://github.com/django/django/pull/12636 made an attempt] at the
deprecation of both `NullBooleanField`'s. I left `NullBooleanSelect` alone
for the time being as it seems like a much larger change. If that's a show
stopper, I can take a swing at that as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/31369#comment:9>
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.24eae887a3e472ebe4eeb51098bae2bf%40djangoproject.com.
