#27917: Allow ModelAdmin.radio_fields to work with NullBooleanField
--------------------------------------+------------------------------------
Reporter: Jerome Leclanche | Owner: Musen
Type: Cleanup/optimization | Status: assigned
Component: contrib.admin | Version: 1.10
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 Musen):
Tim, do you know the status of #23130? It seems to be inactive for 3
years. Do people come to the conclusion to deprecates `NullBooleanField`?
Also, I can see 2 ways to finish the ticket: one to hook NullBooleanField
and create a ChoieField with (('1', 'Unknow'), ('2', ‘Yes'), ('3', 'No')
instead (when it is in `radio_fields`); another is to create a
`NullBooleanRadioSelect` widget to handle this like the original
`NullBooleanSelect` widget. I am not which one is better or there could be
an even better way.
--
Ticket URL: <https://code.djangoproject.com/ticket/27917#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.11c71ba619a72e54e56df3eeefd446c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
