-
Notifications
You must be signed in to change notification settings - Fork 321
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
Add expected pandas 1.5 warning #936
Add expected pandas 1.5 warning #936
Conversation
9ae8f4d
to
d1607c6
Compare
I think it might be worth revisitng how we check for unexpected Sphinx warnings (see #937). But, I think this should be merged ASAP so that the main branch doesn't have failing tests. |
that is surprising, as |
hmm. I am not sure what is happening, but the tests are passing after I removed |
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.
I added a note to investigate what is going on with |
Let's keep tests green. |
Close #935. I didn't see any kitchen-sink warnings, so I replaced
kitchen-sink
withframe.py
in.github/workflows/test.yml
and.github/workflows/prerelease.yml
.