gh-103857: Document utcnow and utcfromtimestamp deprecations in What's New #104542
+11
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re: #103857 (comment), add the deprecations to "What's New in 3.12".
Also fix a typo in a deprecation warning.
And should we clarify these warnings?
It's really
datetime.datetime.utcnow()
anddatetime.datetime.utcfromtimestamp()
, and notdatetime.utcnow()
anddatetime.utcfromtimestamp()
.Reason: to avoid confusion with
datetime.UTC
(which is not reallydatetime.datetime.UTC
).utcnow
andutcfromtimestamp
#103857📚 Documentation preview 📚: https://cpython-previews--104542.org.readthedocs.build/en/104542/whatsnew/3.12.html#deprecated