-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: np.argwhere on pandas series #35331
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
Labels
Comments
1 task
Thanks @rossbar for drawing our attention to this issue. |
I’ve run into this while trying to execute a code that used to work back in 2019. The workaround for anyone stumbling upon this is thus to >>> np.argwhere(s.to_numpy() < 0) |
This looks to work on main now. Could use a test
|
I can jump in and add a test for this. |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
(optional) I have confirmed this bug exists on the master branch of pandas.
numpy/numpy#15555 reports an issue with
np.argwhere
on pandas Series. Reporting here for visibility.MRE:
which, with
numpy.__version__ ==1.20.0.dev0+046a736
gives:pd.version == 0.25.3:
pd.version == 1.0.5:
The text was updated successfully, but these errors were encountered: