On Thu, Jun 30, 2011 at 3:10 PM, Aymeric Augustin <aymeric.augus...@polytechnique.org> wrote: > Strictly speaking, converting a naive datetime + a time zone to a "point in > time" (eg. UTC timestamp) isn't possible, because of DST: one hour doesn't > exist, and another one happens twice. In my opinion, the primary goal of the > DateTime field is to store a "point in time" and it should do so > unambiguously. Of course, we could store a naive datetime plus a time zone > plus a DST flag, but that's cumbersome, I'd even say developer-hostile.
I'm no expert on time zone handling, but shouldn't the two datetimes already have two different timezones in that case? For example, 01:30:00 CDT, followed by 01:30:00 CST an hour later, if the user is in the U.S. Central time zone. Both of those times should be convertible to distinct UTC times. Likewise for the CST to CDT transition in the spring. Cheers, Ian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
