Repository navigation
Fix axes vlines and hlines using wrong coordinates - #25324
Conversation
|
Since this is the second one with it, I don't know what this RR prefix is that you're using on your PR titles. |
Sorry. It's my initials. This is a force of habit thing for me because I'm used to the convention of prefixing branch titles and consequently PRs this way. I will remove the prefix(s) and try to remember not to name PRs this way for this project. |
80089cd to
29e4ea1
Compare
|
Ah, I see. Please remove the prefix from the commit message as well then, as there's an |
930c35b to
e480841
Compare
|
@QuLogic I think I have a solution here that will work to fix this issue. I have it implemented for vlines. I'd be interested to get your feedback on it. If you agree with the approach, I will go ahead and generalize it for hlines. |
8980b9c to
7fa10bf
Compare
oscargus
left a comment
There was a problem hiding this comment.
Looks good!
(I edited the PR message to remove "issue" as "resolves #..." will automatically link this PR with the issue, so upon merging the issue is closed.)
(Seems to be quite a bit of common code in vlines and hlines, but that was the same earlier.)
0541220 to
8397419
Compare
e60dce3 to
217fc0d
Compare
217fc0d to
33c7c2d
Compare
|
@QuLogic I believe all of your comments have been addressed now in the PR. I also rebased the commit. |
|
LGTM, thanks for coming back to this. |
PR Summary
This pr resolves #23171
The vLines and hlines functions are using incorrect coordinates.
The cause of the issue seems to be 2-fold:
PR Checklist
Documentation and Tests
pytestpasses)Release Notes
.. versionadded::directive in the docstring and documented indoc/users/next_whats_new/.. versionchanged::directive in the docstring and documented indoc/api/next_api_changes/next_whats_new/README.rstornext_api_changes/README.rst