#35126: forms.NullBooleanField's validation logic is surprising
------------------------------+--------------------------------------
Reporter: Jeremy Lainé | Owner: Gaurav sah
Type: Bug | Status: closed
Component: Forms | Version: 5.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by Tim Graham):
It seems like a useful improvement, if feasible. Jeremy, it would have
been most helpful if you did some investigation regarding the backwards
compatibility comment rather than simply describing it as "some obscure
reason." Using `git blame` leads to
35a08b8541c856a51b2ab718e0a2fe060debfa2a (#17210). If you're able to
provide a proof of concept solution, feel free to ping me (@timgraham) on
a draft GitHub pull request.
--
Ticket URL: <https://code.djangoproject.com/ticket/35126#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/0107018d22b11be3-c36c6a9f-448f-4da2-9c7f-d2630b54d40e-000000%40eu-central-1.amazonses.com.
