Skip to content

Fix example code for enabling logging in API change notice #18094

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
Jul 28, 2020

Conversation

dopplershift
Copy link
Contributor

PR Summary

I stumbled across that API change when trying to figure out how to turn on logging. The code as provided does not work at all.

  • set_level doesn't exist -> setLevel
  • Nothing appears without setting a handler.

PR Checklist

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

`set_level` doesn't exist, and nothing appears without a handler.
Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
@QuLogic QuLogic added this to the v3.3-doc milestone Jul 28, 2020
@timhoffm
Copy link
Member

CI failure is due to pandas changing a warning (#18101); thus unrelated to this PR.

@timhoffm timhoffm merged commit 11d5b75 into matplotlib:master Jul 28, 2020
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Jul 28, 2020
@dopplershift dopplershift deleted the fix-api-change-logging branch July 29, 2020 00:19
QuLogic added a commit that referenced this pull request Jul 29, 2020
…094-on-v3.3.0-doc

Backport PR #18094 on branch v3.3.0-doc (Fix example code for enabling logging in API change notice)
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