Yeah, the names imply that those should be TZ aware. Though I can understand the reasoning, as this change can silently break already broken code that kind of works, and would be a nightmare to fix in a large codebase.

I also disagree with author, about naive datetime. I don't think there is a good use case for them, and people who use them, do so because they are not aware of the issues.

The only argument I saw was for micro performance improvements, which is kind of funny to care about when programming in python. Since it is implemented in C, the code removing the timezone likely takes more resources.

[–] AlexWIWA@lemmy.ml 5 points 2 years ago

I agree.

The only use I can see for naive date times is you just read the date out of an old sql database, but it shouldn't leave the function naive, it should be converted first.

Python's timezone handling is probably my only complaint about the language. I shouldn't need to use libraries just to have timezones.

[–] jim@programming.dev 4 points 2 years ago (1 children)

While it would be ideal to have all datetime fields in databases and other data stores be time zone aware, that is certainly not the case. Also, SQLite (and probably others) do not have great support for time zones and it's recommended to store datetimes as UTC (typically unix timestamps).

Deprecating utcnow was a good idea, but they should have replaced it with naive_utcnow. Oh well.

[–] BeardedGingerWonder@feddit.uk 5 points 2 years ago (2 children)

Timezones are a disease and should be eradicated. I will die on this hill.

[–] AlexWIWA@lemmy.ml 3 points 2 years ago

I agree. I hate timezones so much

[–] twoframesperminute@mastodon.social -3 points 2 years ago (1 children)

@BeardedGingerWonder will you adapt your time to be 7 hours later?

Thought so.

[–] BeardedGingerWonder@feddit.uk 2 points 2 years ago

You thought what?