I think timezone is also an acceptable spelling, if that's what we've been consistently using, we should probably continue using that.

Alternatively, we could differentiate between datetime.timezone (the class) and the more abstract notion of a "time zone" by including the space for the abstract notion, but I'm more inclined to mark out references to the class with backticks / class references rather than a spelling difference.

I think timezone is also an acceptable spelling, if that's what we've been consistently using, we should probably continue using that.

I'm not sure... the IANA database uses "time zone" and both Wikipedia and The Free Dictionary redirect "timezone" to "time zone"... so maybe "timezone" isn't even valid spelling but people use it anyway?

Alternatively, we could differentiate between datetime.timezone (the class) and the more abstract notion of a "time zone" by including the space for the abstract notion, but I'm more inclined to mark out references to the class with backticks / class references rather than a spelling difference.

Yes, I tried to differentiate all of them (the class and the instances and objects of the class) from the abstract concept.

Hello @erlend-aasland, any issues with this PR?

@uatach, I'll have a look in the next couple of days.

Alternatively, we could differentiate between datetime.timezone (the class) and the more abstract notion of a "time zone" by including the space for the abstract notion, but I'm more inclined to mark out references to the class with backticks / class references rather than a spelling difference.

I think it would be an improvement to consistently use spell it "time zone" in the prose; it would help separate the class from the abstract concept even more.

Both spelling variants are used across the Python docs; I think we would benefit from a consistent spelling all across the docs. Moreover, most dictionaries seem to use "time zone", and as long as that is true, we're bound to get "spelling correction PRs" from time to time.

I created a "time zone" entry in the style guide: python/devguide#1352

Should we also recommend "date and time", or is "datetime" better because it's compact and people will understand what we mean?

Should we also recommend "date and time", or is "datetime" better because it's compact and people will understand what we mean?

With the "time zone" / "timezone" clarification in place, it would also make sense to clarify "datetime" / "date and time", IMO.

Anyway, I read python/devguide#1352 as a blessing from the EB to go forth with this PR.

Sorry it took so long to land this, @uatach; thanks for your good work!

GH-121837 is a backport of this pull request to the 3.13 branch.

GH-121838 is a backport of this pull request to the 3.12 branch.