scheduling: fix scheduling times in UTC timezone instead of local time #160
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.
When using the RecurrentScheduledTime, I would expect to have the time interpreted in UTC.
Conversion between timestamp and datetime is generally depending on the host timezone.
For example:
For a simulation tool, this is rather not expected as this gives different results depending on the host location, so I would rather expect it to use UTC wherever possible.
This is done in this PR, though remaining occurances in test functions of
datetime.timestamp()
are still present.