On 17/08/10 04:24, Russell Keith-Magee wrote: > Adding timezone sensitivity to Django's time/datetime fields is > something that has been on the project to-do list for almost as long > as I've been associated with the project (coming up on 5 years).
Just noting existence of Brian Rosner's django-timezones as a datum, you're very probably already aware of its existence, just mentioning it. http://github.com/brosner/django-timezones Not saying it's perfect, just that it exists and helps us (with some bugfixing) deal with our time zone requirements. But we use postgresql. We always use django settings.TIME_ZONE = 'UTC', settings.TIME_ZONE is what django will currently assume - or tell (postgresql "SET TIME ZONE") the database to use. We _do not_ use settings.TIME_ZONE to determine what final presentation timezone to use for presentation of our (non naive via django-timezones) app-internal datetimes to users. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
