[PR #7302/fde452da backport][3.9] Make max 32-bit timestamp aware #7304
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.
This is a backport of PR #7302 as merged into master (fde452d).
What do these changes do?
Make the max 32-bit timestamp an aware one. For consistency with the non-32-bit one, and to avoid a
DeprecationWarning
with Python 3.12.https://docs.python.org/3.12/library/datetime.html#datetime.datetime.utcfromtimestamp
Are there changes in behavior for the user?
aiohttp.cookiejar.MAX_32BIT_TIME
is now aware. I suppose that's not something directly used much at all though.Related issue number
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.