[FIX] pandas_compat: fix conversion of datetime series #5547
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
datetime.strftime
and specified formats (e.g. pandas output time on nanosecond precision while DateTime only support reading of milliseconds precision max, and some other cases). It could be solvable via some string manipulation which is heavily error prune.Description of changes
timezone
attribute. Storing utc_offset in TimeVariable is also not a good practice since two dates in the same timezone can have two different offsets depending on summer, wintertime or time zones changes in history. Remembering the timezone is more suitable.Includes