-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Running pandas/computation/test_eval individually generates RuntimeWarnings about tp_compare #5039
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
Comments
cc @cpcloud |
We probably should fix this now. It's because there are non-comparable |
@cpcloud ? |
1 similar comment
@cpcloud ? |
weekend :) |
Pushing to 0.14, it's experimental/edge case regardless. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe eval is producing a strange object or something? Or it could be unrelated.
You can see this manifest in a weird sorting difference between numexpr and the flex add method (and this generates the RuntimeWarning shown above).
Somehow they end up with columns in different orders.
The text was updated successfully, but these errors were encountered: