Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Don't split creation of deprecation message and choice of warning class. #12995

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
Dec 28, 2018

Conversation

anntzer
Copy link
Contributor

@anntzer anntzer commented Dec 15, 2018

This avoids duplicating the

category = (PendingDeprecationWarning if pending
            else MatplotlibDeprecationWarning)

logic; right now it's only present twice which is not too bad, but I
plan to add another deprecator (for function arguments) so this is
preliminary work for it.

PR Summary

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/api_changes.rst if API changed in a backward-incompatible way

This avoids duplicating the
```
category = (PendingDeprecationWarning if pending
            else MatplotlibDeprecationWarning)
```
logic; right now it's only present twice which is not too bad, but I
plan to add another deprecator (for function arguments) so this is
preliminary work for it.
@anntzer anntzer added this to the v3.1 milestone Dec 15, 2018
@@ -34,7 +34,7 @@ def _generate_deprecation_message(

if not message:
message = (
"The %(name)s %(obj_type)s"
"\nThe %(name)s %(obj_type)s"
Copy link
Member

Choose a reason for hiding this comment

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

IIRC we had a discussion some time ago that we do not want warnings and logs to introduce newlines.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I didn't want one and still don't, but @dstansby argued in favor of it so there's one right now in warn_deprecated (so I put one here as well) but none in deprecated. I decided to leave it in as I don't care enough to argue about that, but either way it should be consistent between the two cases.

@dstansby dstansby merged commit b94a312 into matplotlib:master Dec 28, 2018
@anntzer anntzer deleted the deprecationwarnings branch December 28, 2018 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.