Hello, I came across the discovery (due to a bug on our code) that it's possible to pass a non-boolean to the __isnull filter. What would be the desired behavior here? Should we raise an exception or should Django use the truthy value?
If the second case is the desired behavior I have found a bug in Django that caused some unexpected behavior. If allowing non-booleans is not desired shouldn't we check for it? I can submit a PR for the specific bug that I found but it would be nice to know if I should. Thanks. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/dcbb5060-c7a1-4363-9564-e79c0ba319e6%40googlegroups.com.
