| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Thank you for opening your first PR into Matplotlib!
If you have not heard from us in a week or so, please leave a new comment below and that should bring it to our attention. Most of our reviewers are volunteers and sometimes things fall through the cracks.
You can also join us on gitter for real-time discussion.
For details on testing, writing docs, and our review process, please see the developer guide
We strive to be a welcoming and open project. Please follow our Code of Conduct.
Sorry, something went wrong.
|
Thanks @gdmcbain! Congratulations on your first PR to Matplotlib 🎉 We hope to hear from you again. @meeseeksdev backport to v3.10.x |
Sorry, something went wrong.
…607-on-v3.10.x Backport PR #29607 on branch v3.10.x (Correct doc for axvline arg x which sets x not y)
…607-on-v3.10.0-doc Backport PR #29607 on branch v3.10.0-doc (Correct doc for axvline arg x which sets x not y)
| Back | FazBrowse Home | New Git URL |
As reported in the issue which this closes #29606 , the docstring for the argument x of axvline says that it sets y, but really it sets x. Perhaps this was a copy'n'paste error from axhline? Where the first argument is y which does set y.
This commit simply emends the doc from y to x to reflect the behaviour.
PR checklist