Repository navigation
Fixed issue #23171 where axes vlines() / hlines() doesn't autoscale correctly with blended transform. - #24695
aalmasmari wants to merge 1 commit into
Conversation
…y with blended transform.
|
@aalmasmari Sorry for the poor response on this. It would be helpful if you included the before and after behaviour change this introduces, and/or added tests to |
|
Moving to draft pending response! Thanks! |
QuLogic
left a comment
There was a problem hiding this comment.
This is not the correct fix, as the wrong values are already added to the data limits. If another thing is plotted afterwards that requests an autoscale of the skipped direction, then the problem will still occur.
|
Hi folks - do we have a way forward here? |
|
I think the correct fix is moving forward in #25324. |
|
Ok. So does this mean this one should be closed, or is there anything we can do here? |
|
Yes, now that I've merged #25324, I think we can close this one. |
PR Summary
Changed vlines() and hlines() of axes to not autoscale on the horizontal/vertical axis given a transform argument. This is so that it doesn't autoscale incorrectly, treating the minimum argument as a data coordinate, as mentioned in issue #23171
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