Skip to content

Improve path.py docstrings a bit #20924

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
Aug 27, 2021
Merged

Conversation

dpoznik
Copy link
Contributor

@dpoznik dpoznik commented Aug 27, 2021

PR Summary

This change fixes some wording in the path.py documentation, most substantively "vertex types" → "path codes". It is a follow-up to #20920 with some issues I noticed after that PR merged.

PR Checklist

  • [N/A] Has pytest style unit tests (and pytest passes).
  • [N/A] Is Flake 8 compliant (run flake8 on changed files to check).
  • [N/A] New features are documented, with examples if plot related.
  • [N/A] Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • [N/A] Conforms to Matplotlib style conventions (install flake8-docstrings and run flake8 --docstring-convention=all).
  • [N/A] New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • [N/A] API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).

@@ -109,7 +109,7 @@ def __init__(self, vertices, codes=None, _interpolation_steps=1,
handled correctly by the Agg PathIterator and other consumers of
path data, such as :meth:`iter_segments`.
codes : array-like or None, optional
n-length array integers representing the codes of the path.
N-length array of integers representing the codes of the path.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Capitalized to match the number of rows in vertices.

@timhoffm timhoffm added this to the v3.5.0 milestone Aug 27, 2021
@timhoffm timhoffm merged commit a931485 into matplotlib:master Aug 27, 2021
@lumberbot-app
Copy link

lumberbot-app bot commented Aug 27, 2021

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
$ git checkout v3.5.x
$ git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
$ git cherry-pick -m1 a9314854fce3cf458630d5257150d5373a9b4037
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
$ git commit -am 'Backport PR #20924: Improve `path.py` docstrings a bit'
  1. Push to a named branch :
git push YOURFORK v3.5.x:auto-backport-of-pr-20924-on-v3.5.x
  1. Create a PR against branch v3.5.x, I would have named this PR:

"Backport PR #20924 on branch v3.5.x (Improve path.py docstrings a bit)"

And apply the correct labels and milestones.

Congratulation you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove Still Needs Manual Backport label once the PR gets merged.

If these instruction are inaccurate, feel free to suggest an improvement.

@timhoffm timhoffm modified the milestones: v3.5.0, v3.6.0 Aug 27, 2021
@dpoznik dpoznik deleted the improve-path-docs branch August 27, 2021 22:09
@QuLogic QuLogic modified the milestones: v3.6.0, v3.5.0 Aug 27, 2021
@QuLogic
Copy link
Member

QuLogic commented Aug 27, 2021

@meeseeksdev backport to v3.5.x

The failure is simply that the previous backport was not merged yet.

meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Aug 27, 2021
tacaswell added a commit that referenced this pull request Aug 28, 2021
…924-on-v3.5.x

Backport PR #20924 on branch v3.5.x (Improve `path.py` docstrings a bit)
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