BUG: to_datetime fails with np.datetime64 and non-ISO format #50038
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MarcoGorelli
force-pushed
the
parse-np-datetime64
branch
2 times, most recently
from
4b76fef to
aa3ad3b
Compare
MarcoGorelli
commented
Dec 3, 2022
Comment on lines
+176
to
+178
| elif is_datetime64_object(val): | ||
| iresult[i] = get_datetime64_nanos(val, NPY_FR_ns) | ||
| continue |
There was a problem hiding this comment.
I'll planning to do more code sharing between the ISO and non-ISO paths, but for now this is a minimal fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.