At least, the behaviour is predictable : it uses `bool(value)`. I believe
it is not a bug but more a question about the input definition: should we
allow non boolean value? I don't see any problem here accepting a string as
a `True` value, it is the job of the user to ensure the value is castabl
Not really related, but it should have been the occasion to announce the
end of the support for Django 1.4, no? According to releases notes, Django
1.4 is not supported anymore six months after the release of Django 1.8.0
in April, so October 1st.
On Sunday, October 4, 2015 at 2:28:36 AM UTC+2,
