Look in the docs here: http://docs.djangoproject.com/en/1.3/ref/settings/#time-zone
As it says, this doesn't work on Window and will result in the system timezone being used. On Mar 29, 8:58 am, aa bb <bietaixiaozh...@gmail.com> wrote: > Hi all! I'm a Django newbie. I set TIME_ZONE to 'UTC' in my project > settings.py. Then I have defined a data model like: > > class D(models.Model): > #some fields > joined_at = models.DateTimeField(null = True, auto_now_add = True) > #some other fields > > I expect when a new D instance is created, its joined_at field will be > a value equivalent to datetime.utcnow(), becuase I set TIME_ZONE to > 'UTC'. But, when I tested it on Windows, I found that it's in fact > datetime.now()! I looked for a while for the reason but nothing > valueble. So please give me a hand if you can. Doesn't UTC time zone > work in Django? Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
