[FIX] Handle timezones in Edit Domain #6123
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.
Issue
Transforming to Time variable fails when timezone is in strings
Description of changes
Correctly handle timezones in data time
Additionally: First I planned to raise the Pandas version to 1.4 since this version already supports subtracting different timezones. It was impossible since Pandas>=1.4 does not support Python 3.7 anymore, so building documentation fails (by readthedcos) since they build documentation on Python 3.7. Setting different versions of python for rtd is supported by the config file, but it cannot be used with multiple subprojects. We cannot raise the Pandas' version until they start supporting config files for subprojects or building on python 3.8.
Includes