News for hackers. Stuff that matters.

A comment on It's Time for a Change: Datetime.utcnow() Is Now Deprecated. Parent comment

Re:It's Time for a Change: Datetime.utcnow() Is Now Deprecated by Spivak on Sunday November 19, 2023 @10:55AM (#38333783)
You still keep everything in UTC in this new world, it's just the object you use internally now knows that it's UTC and makes it so you can't accidentally do calculations on two naive datetimes which happen to be in different timezones.

You get to have the typing help you enforce that everything is in UTC.

[ Parent | on HN ]
Re:It's Time for a Change: Datetime.utcnow() Is Now Deprecated by konschubert on Sunday November 19, 2023 @12:47PM (#38335366)
And you have to treat the timezone offset as information-free.

As in, 02:00+00:00 and 04:00+02:00 are absolutely equivalent representations of the same data.

If you need to know the timezone in which to display a time, you save that timezone separately

[ Parent | on HN ]