Provide an explicit default for BooleanField used in the documentation

[Baptiste Mispelon]

In Django 1.6, we changed the default value for a BooleaField from False to None.
Having a BooleanField without a default now results in warnings when running the validate/check command.

However, our documentation uses some BooleaField in a few examples (see [1] for example) but they don't have a default value.

I propose that all usages of BooleanField in our documentation provide an explicit default (False most likely) so that running the code doesn't raise any warnings.

[1] ​https://docs.djangoproject.com/en/dev/topics/db/models/#multi-table-inheritance

[Collin Anderson]

Feel free to link to the pull request ​https://github.com/django/django/pull/3061. It looks good to me.

[Baptiste Mispelon]

The PR looks good but I found more instances of BooleanField usage (found with git grep "BooleanField(" docs):

• docs/ref/contrib/formtools/form-wizard.txt
• docs/ref/forms/validation.txt
• docs/topics/forms/index.txt

Would you mind fixing those too?
Thanks!

[Tim Graham <timograham@…>]

In 69478859261bd1b3e82cc785fddb5e50e3e7645f:

Fixed #23283 -- Added default=False to BooleanField's in the docs.

Thanks Baptiste for the suggestion.

[Tim Graham <timograham@…>]

In 0f44d9f9b153a25376e57060e849cddfaab9c350:

[1.7.x] Fixed #23283 -- Added default=False to BooleanField's in the docs.

Thanks Baptiste for the suggestion.

Backport of 6947885926 from master

[Baptiste Mispelon]

Oops, looks like I was a bit too slow on the review.

I still think we should fix the remaining 3 (see comment 5) so I'll reopen this ticket.

[Ola Sitarska]

I left them on purpose - these 3 remaining were in forms and I wasn't sure if they're raising the same warnings :)

Here is a pull request with remaining three BooleanFields: ​https://github.com/django/django/pull/3062

[Baptiste Mispelon]

You're absolutely right, my mistake.

Thanks again.