fix pd.to_datetime inferring date incorrectly #13
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.
Hi,
thanks for making this nice python API!
I'm fixing a small bug: when data of
TIME_PERIOD
is presented as integers, e.g., for years, the pandas functionto_datetime
infer incorrectly the value as microseconds from the reference datetime1970-01-01-00:00:00.000
. To fix this, I simply convert the number to string.Working fine with pandas==1.5.3.