On 5/16/2009 10:28 PM, Glenn Maynard wrote: > This is just a quick hack for anyone else bit by this: tzinfo is never > set when reading DateTimeFields out of the database, at least with > Postgresql. > > Now, I have no idea why anyone would want to set TIME_ZONE to anything > but UTC (and the default of an arbitrary US timezone is rather > bizarre), but even with UTC, you need a tzinfo set on your datetimes, > in order to localize them to user time zones with astimezone(). Doing > this manually is a pain--you need to replace(tzinfo=UTC) before every > datetime access.
Hi Glenn, When you get the chance can you review my proposal[1] for fixing DateTimeField in Django? I'm going to try to get this in for 1.2 release. [1] http://code.djangoproject.com/ticket/10587 -- George --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
