Because "required=True" on a BooleanField means "raise a required
validation error if the value is anything other than True" so although
using that combination that would give me the drop down list, it
wouldn't give me the behaviour I desire which is to only raise the
validation error if None is selected. I could handle it on the form,
it just seems to me that given "required=True" is ignored on
NullBooleanField it would be a sensible (and logical) use for it to
have it mean "require the user to pick either Yes or No".
(George - in case this is where you're not clear - in my use case I
don't want the user to be able to just hit the submit button without
having actively selected either "Yes" or "No" for these fields - if
the choices were just "Yes" or "No" then one of those would have to be
the default and thus the default value would be valid so the user
could just hit submit without interacting with the field, whereas if
the selection list includes "Unknown" and defaults to that, the user
has to interact with the field and change it to "Yes" or "No" to pass
validation).
On Jun 17, 12:07 pm, Hanne Moa <
hanne....@gmail.com> wrote: