-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
CI: enable string dtype for test job with pandas main #947
base: main
Are you sure you want to change the base?
CI: enable string dtype for test job with pandas main #947
Conversation
Sorry, that test should of course already have been using the string dtype, because it is using a fixture to enable the option on the fly. So not entirely sure why that is not failing. If I test that example locally in my pandas dev env, it is failing:
Full error traceback:
Now, enabling the future string dtype for the full test suite shows a bunch of other failures (based on a quick look at the logs, I assume most of those failures are things that have to be updated in the tests to run correctly with the future pandas release, for example things like |
Specifically, it's test_gh929 that would fail? |
No, AFAIK that is a test for datetime dtype, it's the |
Currently you still have to enable this manually even when using pandas main (although it is probably time now to switch the default on the pandas side). When enabling this, this should also show that the simple test that was added in #933 is failing again (related to a
np.array(inp, copy=False)
call that now errors ifcopy=False
cannot be honored, this was a change in numpy 2+, that pandas will start following in 3.0)