Avoid checking limits when updating both min and max for contours#26601
Merged
QuLogic merged 2 commits intomatplotlib:mainfrom Sep 6, 2023
Merged
Avoid checking limits when updating both min and max for contours#26601QuLogic merged 2 commits intomatplotlib:mainfrom
QuLogic merged 2 commits intomatplotlib:mainfrom
Conversation
Contributor
|
(The "better fix" I was thinking about was just adding the atomic vmin/vmax update.) |
oscargus
approved these changes
Aug 28, 2023
QuLogic
reviewed
Aug 30, 2023
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Sep 6, 2023
…h min and max for contours
QuLogic
added a commit
that referenced
this pull request
Sep 6, 2023
…601-on-v3.8.x Backport PR #26601 on branch v3.8.x (Avoid checking limits when updating both min and max for contours)
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
closes #26531
In #26531 (comment) @anntzer postulated that a better fix is possible, I'm open to one, but this works.
Note that I think there still could be some problems if updating vlims later on (this only addresses the setting in
__init__).It was also suggested to add an atomic update of both vmin and vmax (which only triggers
changedonce), but that is not yet implemented.PR checklist