skilpat

6 ms·

1.
Kazakhstan and the 25-Hour Leap Day(typesandtimes.net)
2 points by skilpat 3y ago|1 comments
2.
by skilpat 3y ago
Kazakhstan's time zone unification yields an interesting quirk of time. But is it a unique quirk?
3.
Twitter Poll: Which crappy datetime representation do you prefer? Election2020(twitter.com)
1 points by skilpat 6y ago|0 comments
4.
How to Periodize History: 2020 and the Decade Dilemma(typesandtimes.net)
1 points by skilpat 7y ago|0 comments
5.
by skilpat 7y ago
I don't think the London historical offset should be blamed for such errors, nor should New York's nor any other zone's historical, local mean time offsets. If the tzdb is being used in a buggy way, that's on the user -
6.
by skilpat 7y ago
Indeed! That library, as incorporated into the jdk, seems to me like the gold standard of datetime programming in standard libraries. Good type-level distinctions, good defaults, good extensibility... chef kissing fingers
7.
by skilpat 7y ago
That's a pretty wild interpretation! I have nothing but respect for the tz db and its contributors; I indicated as much quite explicitly by stating my appreciation for the commentary. Personally I will soon be sending historical correc
8.
by skilpat 7y ago
I've updated the post to clarify that one should not use `pytz` at all and should instead use `dateutil`. The latter has much more reasonable behavior and is more actively maintained. I also included a link to commentary about pytz by
9.
What the Royal Astronomical Society in 1884 Tells Us About Python Today(typesandtimes.net)
142 points by skilpat 7y ago|48 comments