Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix AnnotationBbox docstring. #15887

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 9, 2019
Merged

Conversation

anntzer
Copy link
Contributor

@anntzer anntzer commented Dec 9, 2019

Yes, it's still not numpydoc because there's a few parameters that I
don't want to figure out (e.g. what does boxcoords really do). The
point is solely that Annotation's xycoords/textcoords also support the
(xvalue, yvalue) tuple form and so it's not specific to AnnotationBbox.

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

Yes, it's still not numpydoc because there's a few parameters that I
don't want to figure out (e.g. what does boxcoords really do).  The
point is solely that Annotation's xycoords/textcoords also support the
(xvalue, yvalue) tuple form and so it's not specific to AnnotationBbox.
@timhoffm timhoffm added this to the v3.3.0 milestone Dec 9, 2019
@timhoffm timhoffm merged commit 04668b7 into matplotlib:master Dec 9, 2019
@anntzer anntzer deleted the annotationbbox-doc branch December 9, 2019 18:47
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.

2 participants