-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Silencing numpy warnings #4369
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
Silencing numpy warnings #4369
Conversation
I think this thread suggests to use |
3b96fb1
to
055d834
Compare
Co-authored-by: keewis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but the linter-enforced else clause seems a bit strange to me
Yeah, I think it makes sense the context of the function alone — it doesn't know that the values are limited to the two parameterizations. Though this fix trades one error for another, in the end. |
isort . && black . && mypy . && flake8
whats-new.rst
Is this the right approach? Or should we be using
np.errstate
machinery?