On Friday, 9 August 2013 01:50:09 UTC+1, Russell Keith-Magee wrote: > > On Fri, Aug 9, 2013 at 1:25 AM, Collin Anderson > <[email protected]<javascript:> > > wrote: > >> The new ./manage check command is for helping people upgrade to a new >> version of django. >> https://docs.djangoproject.com/en/dev/ref/django-admin/#check >> >> django1.6 changes models.BooleanField() to not default to False any more. >> This has already bitten me a few times. >> >> https://docs.djangoproject.com/en/dev/releases/1.6/#booleanfield-no-longer-defaults-to-false >> >> Can we add a warning about BooleanFields without default values to the >> "check" command? >> > > Sounds like a good idea to me - this sort of change is exactly what the > check command is supposed to be identifying (wherever possible). Ticket and > patch welcome! > > I've created a ticket for this #20895 and am working on a patch now.
cheers, Alasdair Nicol > -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
