On 08/19/2015 02:13 PM, Alexander Belopolsky wrote: > > On Wed, Aug 19, 2015 at 1:27 PM, Chris Barker <[email protected] > <mailto:[email protected]>> wrote: > > ISO 8601 does not have a way to encode timezones. > > > I don't have the official $300+ PDF of the standard, but wikipedia > disagrees with you: > <https://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators>.
I think Chris is distinguishing between "timezones" and "UTC offsets". ISO 8601 can certainly encode a UTC offset, but it can't encode a timezone in the sense of "America/New_York". Which is why it's not incorrect at all to say that "2015-03-07 12:00:00-0500" plus 24 hours is "2015-03-08 12:00:00-0500." To claim it should instead be "2015-03-08 13:00:00-0400" is making an unjustified assumption that "UTC-0500" must only mean "America/New_York, not during DST." On the other hand, it's at least arguably incorrect to say that "12:00 March 7 2015 EST" plus 24 hours is "12:00 March 8 2015 EST" rather than "13:00 March 8 2015 EDT". When you're working in terms of a timezone rather than just a UTC offset, there's a reasonable expectation to handle that timezone's DST transitions. Carl
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Datetime-SIG mailing list [email protected] https://mail.python.org/mailman/listinfo/datetime-sig The PSF Code of Conduct applies to this mailing list: https://www.python.org/psf/codeofconduct/
