Proposal: ./manage check to look for models.BooleanField() without default= value.

[Collin Anderson]

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?

[Matthew Lauber]

Maybe do this only for 1.6/1.7 to give a grace period to the change?

--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

[Russell Keith-Magee]

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!

Yours,

Russ Magee %-)

 

[Alasdair Nicol]

I've created a ticket for this #20895 and am working on a patch now.

cheers,

Alasdair Nicol