-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
FIX: Prevent warning when clearing axes with shared non-linear scale #30843
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
Open
saumyacoder1709
wants to merge
4
commits into
matplotlib:main
Choose a base branch
from
saumyacoder1709:fix-clear-shared-log
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+60
−3
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
2e53341
FIX: Prevent warning when clearing axes with shared non-linear scale
b17daeb
Add test for clearing shared non-linear axes without warning
7c07652
Merge branch 'main' into fix-clear-shared-log
saumyacoder1709 476b3ef
Clean up blank lines in test_shared_axes_clear_with_nonlinear_scale
saumyacoder1709 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please convince me that this is the correct solution and not just fixing a special case. I don’t have full oversight on the details of the topic, but doing selective action on scale and limits doesn’t feel like it it’s a general solution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pushing back on this—it's a fair concern! Let me explain why I think this is actually a proper fix rather than just patching one edge case.
The core idea:
The problem we're solving is: when you clear an axes, it shouldn't try to force invalid default values onto other axes that share with it. My fix prevents exactly that—it stops (0, 1) limits from being passed to axes with non-linear scales that can't handle them.
Why focus on (0, 1)?
Those are the hardcoded default limits that [clear()] uses (you can see this on line 1427 in [_base.py]. They're literally the only values that would cause this issue during a clear operation. So checking specifically for (0, 1) isn't narrowing the fix—it's targeting the exact source of the problem.
What about other non-linear scales?
The condition [other_axis.get_scale() != 'linear'] handles everything: log, logit, symlog, asinh—any scale that isn't linear. They all have their own domain restrictions, and (0, 1) is problematic for many of them. So this actually covers all the cases where this warning could appear.
Why fix it in the propagation logic?
I chose this spot because it's where shared axes sync up their limits. When one axis changes its limits, it tells its shared partners. By catching the issue here, we prevent bad values from even reaching the point where they'd trigger warnings. It felt cleaner than trying to suppress warnings or changing how [clear()] itself works.
What I tried first:
I actually started by using [emit=False] when clearing, which would just stop all propagation. But that broke a different feature—when you clear an inverted shared axis, the other axes need to get that update. So [emit=False] was too heavy-handed.