Allow constructing boxplots over multiple calls. #13444
Merged
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.
Currently, calls to boxplot() set the axis limits, ticks, and ticklabels
assuming that nothing else, and in particular no other boxplot, will be
drawn on the axis; e.g., after
the xlims will be moved to hide the first boxplot, and even after
manually resetting the xlims, the tick at x=3 and its label will be gone
too.
Fix that to make boxplot a bit more cooperative with previous calls:
instead of forcefully setting the axis limits, just update the dataLim
and let autoscaling handle axis limits; also check whether the axis
already has a FixedLocator/FixedFormatter and if so, just append the new
tick locations and labels.
Also rename manage_xticks to manage_ticks (with deprecation), as the
direction it manages depends on the vert kwarg (discussed in #13435).
attn @phobson I guess.
PR Summary
PR Checklist