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

2013-08-11 Thread Alasdair Nicol
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 > > wrote: > >> The new ./manage check command is for helping people upgrade to a new >> version of django. >>

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

2013-08-08 Thread Russell Keith-Magee
On Fri, Aug 9, 2013 at 1:25 AM, Collin Anderson 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

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

2013-08-08 Thread Matthew Lauber
Maybe do this only for 1.6/1.7 to give a grace period to the change? On Thu, Aug 8, 2013 at 1:25 PM, Collin Anderson wrote: > The new ./manage check command is for helping people upgrade to a new > version of django. >

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

2013-08-08 Thread 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.