Deprecate trying to set minor ticks in 3D #15003
Closed
Conversation
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
0e87111 to
702d242
Compare
702d242 to
5599b98
Compare
|
#14626 adds support for minor ticks in 3d axes. |
|
🐑 Is that ready for review? |
|
Yes. |
|
Obsolete because of #14626. |
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
they are not supported anyway. It's better to warn now and fail in the future than to silently do nothing. The ultimate plan is to drop the
minorparameter in the future so that we have a clean API at least.set_zticks(*args, **kwargs)to to explicit parameters.set_zticks(set_xticks/yticksdoes this already).Inspired from user problems in #14980.