[Chris Barker] >> Maybe I'm getting hung up on purity over practicality -- but this sure seem >> slike logic that should not be in the timezone object -- it has nothing to >> do with time zones.
[Alexander Belopolsky] > It has everything to do with timezones. The information about > historical addition of leap seconds is and will be distributed with > the timezone databases. This is what Olson's distribution has always > done and what IANA intends to continue. See [1] for more details. > > [1]: https://tools.ietf.org/html/draft-ietf-tzdist-service-11#section-5.6 A "timezone" _now_ should really be defined as an offset from TAI, the one remaining scheme that remains - and always will remain - utterly uniform. Then it would make perfect sense to everyone that the history of UTC leap seconds, which are changes to UTC's offset from TAI, belong in timezone logic. Then again, everything looks simple to me - LOL ;-) _______________________________________________ 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/
