Re: Django migrations and DateTimeField defaults

2014-08-13 Thread Andy Roxby
Thanks, that's what I did. In my humble opinion, the ValueError should be removed and the timezone serialized in the form UTC offset (eg: -0400). On Tuesday, August 12, 2014 9:43:11 PM UTC-4, Collin Anderson wrote: > > Wow. That almost sounds like a bug, though you can however use a callable. >

Re: Django migrations and DateTimeField defaults

2014-08-12 Thread Collin Anderson
Wow. That almost sounds like a bug, though you can however use a callable. As ridiculous as it looks, it should work :). INF_TIME = datetime.max.replace(tzinfo=timezone.utc) def get_inf_time(): return INF_TIME death = models.DateTimeField(default=get_inf_time) What you are doing seems pret

Django migrations and DateTimeField defaults

2014-08-12 Thread Andy Roxby
Hello all, I'm new to this list so please let me know I'm overlooking any sort of e tiquette. I'm having problem trying to use a default value for a DateTimeField. When I specify a default value WITH a timezone I receive the following error during './manage.py makemigrations' ValueError: Cannot