Fixes #1530: Replace deprecated utcnow and utcfromtimestamp with timezone-aware datetime #1531
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jim-vl
force-pushed
the
fix/utcnow-deprecation-1530
branch
from
8ff6f63 to
3bd4bab
Compare
jim-vl
force-pushed
the
fix/utcnow-deprecation-1530
branch
from
3bd4bab to
0fcb361
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #1530
Replaces all uses of 'datetime.utcnow()' and 'datetime.utcfromtimestamp()' with timezone-aware 'datetime.now(timezone.utc)' to address the deprecation warning.
Test added and updated.
This is my first PR, happy to receive feedback!