News for hackers. Stuff that matters.
Re:Ten Python datetime pitfalls, and what libraries are (not... by lijok on Sunday February 18, 2024 @12:51PM (#39421240)
Unfortunately timezones have the nasty ability to change.

See: https://codeblog.jonskeet.uk/2019/03/27/storing-utc-is-not-a...

Re:Ten Python datetime pitfalls, and what libraries are (not... by Hackbraten on Sunday February 18, 2024 @03:46PM (#39423115)
That's why they wrote "state the actual timezone" and not "state the actual UTC offset."

Actual timezone would mean "2025-01-01 16:00:00 Europe/Berlin," not just "2025-01-01 16:00:00 +01:00."

Re:Ten Python datetime pitfalls, and what libraries are (not... by lijok on Sunday February 18, 2024 @03:55PM (#39423228)
Even those change
Re:Ten Python datetime pitfalls, and what libraries are (not... by Hackbraten on Sunday February 18, 2024 @04:34PM (#39423619)
I agree. The city where the cafe is located might be annexed or usurped by another country, and have another timezone imposed on it.

Handling that kind of change would be beyond impractical though?

Re:Ten Python datetime pitfalls, and what libraries are (not... by lijok on Sunday February 18, 2024 @06:04PM (#39424431)
Good question. I wonder what impact timezone wise the annexation of Crimea had on hypergiants like FAANG. I can imagine some weirdness when rerunning say historical domain events to hydrate a new service.

Wonder if they have libraries to handle such edgecases