Skip to content
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

MAINT: Add python 3.6 support to suppress_warnings #8177

Merged
merged 1 commit into from
Oct 19, 2016

Conversation

seberg
Copy link
Member

@seberg seberg commented Oct 19, 2016

Python 3.6 has two methods for showing warnings, so we have to support
both ways (strictly speaking, on python 3.6 itself only the new would
probably be needed).

Also adds the _filters_mutated() call to replace manual registry
clearing. This is basically the fix that newer python versions have
to avoid the issue making the manual clearing unnecessary.

Closes gh-8176

Python 3.6 has two methods for showing warnings, so we have to support
both ways (strictly speaking, on python 3.6 itself only the new would
probably be needed).

Also adds the _filters_mutated() call to replace manual registry
clearing. This is basically the fix that newer python versions have
to avoid the issue making the manual clearing unnecessary.

Closes numpygh-8176
@seberg
Copy link
Member Author

seberg commented Oct 19, 2016

For the curious, I commented on the python issue about the introduction that a release note would have been nice. I am also not 100% sure if they already decided whether to leave the function with a leading underscore or not.

@seberg
Copy link
Member Author

seberg commented Oct 19, 2016

Btw. just saw that it seems that by default, if you create a merge request, you make the branch accessible for the upstream devs. Not sure if its worth much, but could avoid a full creation of a new PR in some cases.

@seberg
Copy link
Member Author

seberg commented Oct 19, 2016

Also, especially for cleaning up (with forced push), it could be annoying also.

@charris charris merged commit 6da5f00 into numpy:master Oct 19, 2016
@charris
Copy link
Member

charris commented Oct 19, 2016

Thanks Sebastian, that was quick. Yes, it would have helped if the change had been mentioned in the 3.6 release notes.

@charris charris added this to the 1.12.0 release milestone Oct 19, 2016
@seberg seberg deleted the issue8176 branch October 19, 2016 15:46
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.

Test failures on Python 3.6.0b2
2 participants