The current behaviour of BooleanField kind of negates the need for NullBooleanField.
Contrary to the docs (and I'm pretty sure there's a ticket for it) a BooleanField(required=True) doesn't actually fail validation if a widget. Personally, I like this behaviour better. Would we be losing any functionality if we just had a BooleanField that behaved as NullBooleanField does now? A side note, while I'm looking at the code I see that the clean method of BooleanField is a bit ugly. It'd be better to handle that if value == 'False' as a custom hidden widget. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
