#10928: BooleanField: different behaviour when default=callable
-------------------------------------+--------------------------------------
Reporter: a...@gc-web.de | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by a...@gc-web.de):
Ok, I found out that I can work around by returning None instead of False
from the callable, the value="" attribute is left out in the hidden
initial. A possible fix would be to make the CheckboxInput widget accept
{{{u"False"}}} as {{{False}}} in the _has_changed check, or by preventing
the hidden initial field from having value="False" in the first place.
--
Ticket URL: <http://code.djangoproject.com/ticket/10928#comment:2>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
