Psst. Next year is a leap year. Depending on your deployment story, now (or 3 months ago😅) might be a good time to start looking into logic that won't handle leap years correctly.
and we only have 4 years left (*) to adopt the calendar that skips the leap year every 128 years -- simpler and more accurate than the Gregorian fix.
... yes we could do this at any time, but the advantage of skipping in 2028 is this matches Gregorian back to 1800, which is not too far off when Britain switched from Julian in the first place (1752), i.e., far enough back that there's confusion anyway.
... whereas if we wait until 2100, then we're only matching Gregorian back to 1972, meaning dates in the CLib/Internet Epoch [1/1/1970] will be affected
(2048 ["years divisible by 128"] is the other obvious year to start; in that case, we're good back to 1920)
(*) yeah, not betting the farm on this happening.
@wrog Interesting, though I think the Gregorian calendar is Good Enough™ at this point, and changing calendars would do more harm than good.
We won't be out of sync with the solar year by a margin of one day for another 2900 years. By then I fully expect us to either be extinct or at a level of technology where the seasons on Earth are not that important. Even if they are, there are still tens of thousands of years before things other than "hmm, the equinoxes seem to be off by a day" start to become obvious.
yeah, this is more of an If I Were Dictator thing (I'm far more worried about the concept of leap seconds not dying out soon enough)
though things are going to be somewhat fun when Gregorian and Revised Julian get out of sync (2800 AD), assuming Catholic vs. Orthodox is still a thing then.
Bugs like `dt.replace(year=dt.year + 1)`, code that works with ordinal day-of-year, etc.