TST: Add regression test for to_datetime format gh-54958 #62397
Closed
+16
−0
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
|
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
This is a PR and I don't see the relation of your tests with it. Please verify if it is correct. |
I am closing this PR. It was submitted in error and references a non-existent issue. My apologies for the noise. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #54958
Adds a regression test to ensure that
pd.to_datetimewith a specific format does not fail on strings that are longer than the format implies.Note: I was unable to run the test suite locally as the
mainbranch currently fails to build on my Windows machine (with thefree_threading_config.pxierror). The automated tests (CI) should be able to verify this change.