Merged
Conversation
Use timezone-aware date wherever possible, else `datetime.utcnow()`.
Converts the remaining parts of DP3 to use tz-aware datetimes. BREAKING: The API date output is now in UTC, RFC 3339 format.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR addresses two issues:
utcnow(), which was deprecated in python3.12Before this change, some timestamps were set by
datetime.now(), even though DP3 implicitly assumes UTC time from all its input modules. The outputs were also implicitly converted UTC, but tz-naive, which needed extra handling to work.