refactor: replace deprecated datetime.utcnow with datetime.now(timezo… #480
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.
❤️ Thank you for your contribution!
Description
Note:
A decision should be made whether to keep naive datetime objects or switch to timezone-aware datetimes.
Using timezone-aware objects like
datetime.now(timezone.utc)
ensures future compatibility and avoids the upcoming deprecation ofdatetime.utcnow()
.For now, this PR performs a drop-in replacement with
datetime.now(timezone.utc).replace(tzinfo=None)
to retain compatibility with the existing naive datetime usage,without altering the current behavior or implementation. Future revisions should consider full timezone awareness for better clarity and accuracy in time handling.
Once approved, we can proceed with updating the remaining packages.
Checklist
Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:
Frontend
Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that: