8000 TST: Ignore deprecations when switching backends. by QuLogic · Pull Request #17963 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

TST: Ignore deprecations when switching backends. #17963

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 1 commit into from
Jul 22, 2020

Conversation

QuLogic
Copy link
Member
@QuLogic QuLogic commented Jul 19, 2020

PR Summary

Otherwise, stuff like Qt4 backend cannot be tested because the deprecation warning will cause a failure.

PR Checklist

  • Has Pytest style unit tests
  • Code is Flake 8 compliant
  • [N/A] New features are documented, with examples if plot related
  • [N/A] Documentation is sphinx and numpydoc compliant
  • [N/A] Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • [N/A] Documented in doc/api/next_api_changes/* if API changed in a backward-incompatible way

Otherwise, stuff like Qt4 backend cannot be tested because the
deprecation warning will cause a failure.
@QuLogic QuLogic added this to the v3.3.1 milestone Jul 19, 2020
Copy link
Member
@jklymak jklymak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a testing expert, but seems reasonable to me

@tacaswell tacaswell merged commit e2fbf41 into matplotlib:master Jul 22, 2020
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Jul 22, 2020
@QuLogic QuLogic deleted the backend-deprecations branch July 22, 2020 19:53
timhoffm added a commit that referenced this pull request Jul 22, 2020
…963-on-v3.3.x

Backport PR #17963 on branch v3.3.x (TST: Ignore deprecations when switching backends.)
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.

3 participants
0