#15124: BooleanField should not use False as default (unless provided) -------------------------------------+------------------------------------- Reporter: andrewbadr | Owner: aaugustin Type: Bug | Status: closed Component: Database layer | Version: (models, ORM) | 1.4-alpha-1 Severity: Normal | Resolution: fixed Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: new => closed * resolution: => fixed Comment: In [changeset:"e16c48e001ccd06830bb0bfd1d20e22ec30fce59"]: {{{ #!CommitTicketReference repository="" revision="e16c48e001ccd06830bb0bfd1d20e22ec30fce59" Fixed #15124 -- Changed the default for BooleanField. Thanks to the many contributors who updated and improved the patch over the life of this ticket. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/15124#comment:17> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.