Explain ephemeral nature of Tick instances#31712
Open
jayaprajapatii wants to merge 1 commit into
Open
Conversation
4b686d7 to
27ac3ed
Compare
Member
|
I think this needs details about when ticks are regenerated. Then someone who does have a rare need to modify individual ticks can make sure to do so after the last (re)generation. Just telling them to be aware that things might change is not practical guidance. |
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
2 participants
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.
Closes #31697
Summary
Adds a short documentation section explaining the ephemeral nature of
.axis.Tickinstances and why.Axes.tick_paramsis generally preferred over modifying individual ticks directly.The new section also mentions that direct modifications to individual tick Artists may not persist when ticks are regenerated.
Verification
make html