4 ms·
> the almanac actually changes based on laws and stuff. some of my perennial favorites: - in samoa, there was never a december 30th 2011. - in indiana, time
by hprotagonist 3y ago
> the almanac actually changes based on laws and stuff.
some of my perennial favorites:
- in samoa, there was never a december 30th 2011.
- in indiana, time zone observance is determined per county
- in arizona, the reservation land observes dst, and the state doesn’t, and reservation lands can enclose non-reservation lands.
- lebanon recently had a legislative dispute about dst such that some entities in the nation did or did not observe dst for about a week.
- cudder 3y ago> - in samoa, there was never a december 30th 2011. That was interesting, so I had to read about it. Apparently they skipped a day to be closer to Asian time zones. They did the same thing in the opposite direction in 1892 by having two 4th of Julys to be closer to American timezones. Now they kinda just walked back on that. Interestingly I think the Python datetime approach can handle both of these with no problem. The rest of your list sounds... a lot tougher.
- RobotToaster 3y agoIf you're storing historical dates, September 1752 only had 19 days.
- hprotagonist 3y agooh, historical time is an absolute mess. i have yet to find a library that handles BC dates except maybe astropy — and they have different priorities!
- remram 3y agoThe transition from the Julian to Gregorian calendar also happened on vastly different dates in different countries. Most of Western Europe changed in 1582, the British Empire (and its American colonies) in 1752 as you said, and other countries switched even later like Russia in 1918.