News for hackers. Stuff that matters.
Re:Ten Python datetime pitfalls, and what libraries are (not... by ariebovenberg on Tuesday February 20, 2024 @05:59AM (#39439842)
You are correct that there are improvements to be made. The current internal representation is—for the moment—simply the Python standard library.

Probably the approach of Chrono is best: allow leap seconds to be represented (i.e. 23:59:60), but not to account for them historically.

There are no comments on this comment yet.