TST: add regression tests for interpolate(method="time") with nullable dtypes (GH#40252) #62571
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
jonathan-gut
changed the title
Contributor
|
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this implement/fix?
This PR adds regression tests ensuring that
DataFrame.interpolate(method="time")works correctly with nullableInt64andFloat64dtypes.The original issue (#40252) reported that
interpolate(method="time")raised a ValueError for these dtypes. On currentmain, the behavior is correct, but no dedicated tests existed. These tests safeguard against future regressions.Changes
test_interpolate_time_with_nullable_int64test_interpolate_time_with_nullable_float64Notes
No user-facing API change. Strictly test coverage.