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.
GH-51301: Fix deprecation warnings in the tests with numpy/pandas nightly #51404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
GH-51301: Fix deprecation warnings in the tests with numpy/pandas nightly #51404
Changes from all commits
1ed3c25b2d348a180c88143de55d0baa24284a851854feb6da148c134fa9481File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this makes the test run without the warning, I am not sure if then the surrounding asserts still make sense.
One thing to do is also to change
expected = np.dtype('m8')to use "m8[s]", but no idea if that would then still have produced the initial bug (the reason this test was added, #13553)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, OK, sorry. Didn't try locally and assumed
np.dtype(np.timedelta64)produces same result for any unit. I am guessing we want to keep testing this even for higher numpy versions. Will look first into changingexpectedvalue and what that means for the initial bug.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From testing locally it seems the initial bug is not produced even if using a time unit everywhere. Will push a commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a148c13
Uh oh!
There was an error while loading. Please reload this page.