3 ms·
If you've not read the blog post that explains why this library exists I recommend it. It's called "Ten Python datetime pitfalls, and what libraries are (not) d
by Hasnep 1y ago
If you've not read the blog post that explains why this library exists I recommend it. It's called "Ten Python datetime pitfalls, and what libraries are (not) doing about it"
https://dev.arie.bovenberg.net/blog/python-datetime-pitfalls/ https://dev.arie.bovenberg.net/blog/python-datetime-pitfalls...
- JodieBenitez 1y agoExcellent read.
- jwilk 1y agoDiscussed on HN back then: https://news.ycombinator.com/item?id=39417231 https://news.ycombinator.com/item?id=39417231 (147 comments)
- mdaniel 1y agohttps://dev.arie.bovenberg.net/blog/python-datetime-pitfalls/#5-guessing-in-the-face-of-ambiguity https://dev.arie.bovenberg.net/blog/python-datetime-pitfalls... highlighted yet another thing that I hadn't previously considered and makes me plug <https://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time https://infiniteundo.com/post/25326999628/falsehoods-program...> <https://news.ycombinator.com/item?id=4128208 https://news.ycombinator.com/item?id=4128208>
- barbazoo 1y agoI am a seasoned programmer but whenever I deal with datetime objects I do my best with unit tests and then just hope none of these “edge” cases apply to us. Meaning: I have no idea really how it works under the hood. Now at least there’s an LLM that might spot a bug every now and then so that’s nice.
- deleted 1y ago[deleted]