Fix DatetimeRange timestamp iteration #17
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.
Problem:
DatetimeRange.iter_timestamps()
does not return the correct time series when the starting timestamp is tz-aware and in a timezone with DST.Currently the function produces the following at spring-forward:
It needs to be:
Solution: Advance timestamp in standard timezone (e.g., UTC) and convert back to input timezone before yielding.
Also fixed
DatetimeRange.list_timestamps_from_dataframe()
to return unique timestamps only. Do we need sort it?Did not fix relevant pytests