On Apr 27, 2010, at 3:36 PM, Peter Herndon wrote: > Hi Shawn, > > http://pytz.sourceforge.net/ looks like it would be useful for converting > time zone strings. > > The one thing I keep hearing, though, whenever anyone brings up time zones > here on django-users is: "*ALWAYS* store dates in UTC, then convert as > needed". Don't know how useful that is, but for what it's worth, *whump*, > there it is. :) > > ---Peter Herndon
Thanks for the tip on pytz. It might be what I need. As for the other part of your note, I completely agree with the sentiment. The problem is that, in a standard Django installation, there's an inherent timezone defined in settings.py. Given a time from a third party, with a known (different) time zone, it still has to be converted to UTC or the local timezone, and for that I need to be able to derive a timedelta from those verbose time zone names. Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
