Deprecate axis_artist.BezierPath. #14786
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.
Throughout the library the advice to draw an arbitrary Path object is to
use PathPatch; there's no reason to do differently with a one-off class
in axisartist.
Technically that's an API break because the type of AxisArtist.line
changed, but most common APIs do overlap (e.g.
set_color
, which isexercised by the tests) so I'm not going to bother with a deprecation
period which would be quite painful (likely involving a global rcParam
controlling the switch from the old API to the new one).
PR Summary
PR Checklist