-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
REGR: comparison op with dask data structure fails #38946
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
Checked and this was still working in 1.1.x, and started to fail for pandas 1.2.0 |
Bisecting gives 40daf00 is the first bad commit
|
Hmm, it seems that this before only worked for categorical (at least testing the above example but using int64 or object dtype, I get all False or an error, respectively, also on previous released versions of pandas). So probably not a priority for 1.2.x |
Looks like |
moved to 1.2.2 |
moved to 1.2.3 |
@TomAugspurger suggestions for what attribute to check to determine we should return NotImplemented? |
moved to 1.2.5 |
removing milestone. |
Following #48347, it is up to dask to define |
Using pandas 1.0.5 and latest dask 2020.12.0:
But with master (using same dask version), this gives:
The text was updated successfully, but these errors were encountered: