Re:No leap second will be introduced at the end of June 2026
by caymanjim on Tuesday March 10, 2026 @01:42AM
(#47319448)
I just had a Y10K problem. Customer data was using 9999-12-31 23:59:59 as a placeholder value, and our app crashed converting from the customer's timezone to UTC. I learned that Python datetime can't handle Y10K.
[ Parent
| on HN ]
There are no comments on this comment yet.