You still keep everything in UTC in this new world, it's just the object you use... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

Spivak on Nov 19, 2023 | parent | context | favorite | on: datetime.utcnow() is now deprecated

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.

konschubert on Nov 19, 2023 [–]

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

Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact