Repository navigation
Clarify SecondaryAxes limit behavior via documentation - #31439
Merged
timhoffm merged 1 commit intoApr 2, 2026
Merged
timhoffm merged 1 commit into
timhoffm merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
|
@timhoffm Documentation added as per the requirement and valuable suggestion given by you. |
Sorry, something went wrong.
timhoffm
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR summary
This PR updates the documentation to clarify how limits behave for SecondaryAxes. It might just help to mention in the docs that setting its limits (like set_xlim/set_ylim) has no effect, since the current silent behaviour can be a bit confusing.
Following the discussion in the issue, this change adds a note in the Returns section to make this behaviour explicit.
AI Disclosure
PR checklist