remove utcnow() calls to fix deprecation warnings encountered in python 3.12
#3093
Conversation
This file contains 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
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #3093 +/- ##
========================================
Coverage 93.14% 93.14%
========================================
Files 66 66
Lines 14237 14238 +1
========================================
+ Hits 13261 13262 +1
Misses 976 976 ☔ View full report in Codecov by Sentry. |
|
Resolving for inclusion at a later date. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Replace
utcnow()withnow(datetime.timezone.utc). Integ tests were run successfully on my local machine. One deprecation warning frompython-dateutilis still expected in GitHub CI. The unknown timezone warning is a separate issue that should be addressed in another PR.