Fix tzlocal issue #1126
Merged
Fix tzlocal issue #1126
Conversation
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
f6c2464 to
6b0a949
Compare
WhyNotHugo
approved these changes
May 5, 2022
23d70f5 to
415ee2f
Compare
WhyNotHugo
approved these changes
May 5, 2022
d7415
approved these changes
May 7, 2022
Newer versions of tzlocal return tzinfo timezones, not pytz ones. Khal can't deal with tzinfo timezones for the moment, so we force pytz timezones when we use tzlocal. This should be removed when we completely migrate to tzinfo. Fix #1092
This was referenced May 7, 2022
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.
Newer versions of tzlocal return tzinfo timezones, not pytz ones. Khal
can't deal with tzinfo timezones for the moment, so we force pytz
timezones when we use tzlocal.
This should be removed when we completely migrate to tzinfo.
Fix #1092 #1087