8000 DOC: fix API note about get_tightbbox by jklymak · Pull Request #12186 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

DOC: fix API note about get_tightbbox #12186

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
Sep 21, 2018

Conversation

jklymak
Copy link
Member
@jklymak jklymak commented Sep 20, 2018

PR Summary

Made against 3.0.0-doc, but not sure that is correct. master...

See discsuiion on gitter. I forgot to mention in the API change for axes.get_tightbbox that we'd added a kwarg.

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

Copy link
Contributor
@astrofrog astrofrog left a comment

Choose a reason for hiding this comment

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

Looks good!

@tacaswell
Copy link
Member

Lets stick with PRs to master and backporting via the bot.

It makes sense to do either lots of merge-ups (from 3.0.0-doc -> 3.0.x -> master) or to do lots of backports, but not both. I think we will still do occasional merges up (so that you can see tags from the master branch so versioneer works correctly) but use the backports as the primary way of moving things between branches.

@tacaswell tacaswell changed the base branch from v3.0.0-doc to master September 20, 2018 18:48
@tacaswell tacaswell changed the base branch from master to v3.0.0-doc September 20, 2018 18:48
@tacaswell
Copy link
Member

hmm, tried changing the base and that went...badly.

@jklymak jklymak changed the base branch from v3.0.0-doc to v3.0.x September 20, 2018 19:51
@jklymak jklymak changed the base branch from v3.0.x to master September 20, 2018 19:53
@jklymak
Copy link
Member Author
jklymak commented Sep 20, 2018

Somehow that entry got removed from master. I think I've fixed it now for basing it on master...

@jklymak jklymak added this to the v3.0.0-doc milestone Sep 20, 2018
@jklymak
Copy link
Member Author
jklymak commented Sep 20, 2018

.. and hard cycling...

@jklymak jklymak closed this Sep 20, 2018
@jklymak jklymak reopened this Sep 20, 2018
returned by `.matplotlib.axes.Axes.get_tightbbox`.

`.matplotlib.axes.Axes.get_tightbbox` adds a new kwarg ``bbox_extra_artists``
to specify the manually list of artists on the axes to include in the
Copy link
Member

Choose a reason for hiding this comment

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

not a native speaker, but I feel the "manually" should either be an adjective rather than an adverb or be in another position in the sentence.

Copy link
Member Author

Choose a reason for hiding this comment

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

Agreed!

@tacaswell tacaswell merged commit 09e9504 into matplotlib:master Sep 21, 2018
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Sep 21, 2018
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Sep 21, 2018
@jklymak jklymak deleted the doc-fix-api-change branch September 21, 2018 19:24
tacaswell added a commit that referenced this pull request Sep 21, 2018
…186-on-v3.0.0-doc

Backport PR #12186 on branch v3.0.0-doc (DOC: fix API note about get_tightbbox)
NelleV added a commit that referenced this pull request Sep 21, 2018
…186-on-v3.0.x

Backport PR #12186 on branch v3.0.x (DOC: fix API note about get_tightbbox)
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.

4 participants
0