Use timezone.utc instead of pytz.utc #49
Merged
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
These both should equal to 0 as far as tzinfo structure is concerned, so there is no need to require pytz just to express utc timezone
|
@fitnr just checking if you've seen this 🙏 |
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.
Both pytz.utc and timezone.utc should equal to an offset/dst of 0, as far as tzinfo structure is concerned, so there is no need to require pytz just to express utc timezone (as far as I'm aware).
Note: tox failed locally only for 3.9, seemingly because it didn't install pymeeus , not sure if this is expected or not.