#23283: Provide an explicit default for BooleanField used in the documentation
------------------------------------------------+------------------------
Reporter: bmispelon | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
------------------------------------------------+------------------------
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
--
Ticket URL: <https://code.djangoproject.com/ticket/23283>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.eb79ad5e26a75195cb711752ef1d1d9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
