Skip to content

MAINT: Increment stacklevel for warnings to account for NEP-18 overrides #13589

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

Merged
merged 2 commits into from
May 20, 2019

Conversation

shoyer
Copy link
Member

@shoyer shoyer commented May 19, 2019

For NumPy functions that make use of __array_function__, the appropriate the
stack level for warnings should generally be increased by 1 to account for
the override function defined in numpy.core.overrides.

Fixes GH-13329

For NumPy functions that make use of `__array_function__`, the appropriate the
stack level for warnings should generally be increased by 1 to account for
the override function defined in numpy.core.overrides.

Fixes numpyGH-13329
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
@shoyer shoyer merged commit f9c1502 into numpy:master May 20, 2019
@shoyer shoyer deleted the nep-18-warnings-increment branch May 20, 2019 16:37
@seberg seberg changed the title Increment stacklevel for warnings to account for NEP-18 overrides MAINT: Increment stacklevel for warnings to account for NEP-18 overrides May 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Warnings need different stacklevel after NEP 18 overrides
3 participants