-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Pandas 0.25.0 breaks np.isin #31080
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
i suppose; we have literally 0 support for this now welcome to have a PR which patches with tests |
Thanks for the answer. Any ideas how you would approach this ? |
i have no idea what np.isin actually does with non numpy types; not even sure why you would want to do this; Series.isin is well supported, tested and type aware we do have numpy ufunc compatibility but don’t know how np.isin behaves |
On a quick investigation it does look like a pandas issue.
it basically does..
|
Observed with numpy 1.17.4 as well as (latest) 1.18.1:
Problem description
Since 0.25.0, the
==
ofpd.Timestamp
is preserved but it doesn't go throughnp.isin
.This is observed as well under pandas 0.25.3.
The text was updated successfully, but these errors were encountered: