Remove deprecated naive datetime warnings #9895
Merged
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.
DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
These warnings were appearing ~4000 times in test results,
datetime.utcnow()
is deprecated in Python 3.12For some background: https://blog.miguelgrinberg.com/post/it-s-time-for-a-change-datetime-utcnow-is-now-deprecated
This fixes the warnings caused by code in this repo. I think it doesn't introduce any new problems, but
utcnow()
was used in a range of places, having others review these changes would be helpful, in case there is a subtle impact from format changes I have missed.BEFORE:
2162 passed, 9 skipped, 9 xfailed, 4891 warnings in 6.21s
AFTER:
2162 passed, 9 skipped, 9 xfailed, 20 warnings in 6.18s
Remaining utcnow() deprecation warnings are in external repos: Infogami and webpy:
Closes #
Technical
Testing
Screenshot
Stakeholders