Skip to content

Clarify behavior of prune parameter to MaxNLocator. #27276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 6, 2023

Conversation

anntzer
Copy link
Contributor

@anntzer anntzer commented Nov 6, 2023

Closes #27274.

PR summary

PR checklist

Copy link
Member

@rcomer rcomer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clearer and more concise. Nice.

@rcomer rcomer added this to the v3.8.2 milestone Nov 6, 2023
@story645 story645 added the Documentation: API files in lib/ and doc/api label Nov 6, 2023
@story645 story645 merged commit 66b9952 into matplotlib:main Nov 6, 2023
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Nov 6, 2023
@anntzer anntzer deleted the dp branch November 6, 2023 21:03
story645 added a commit that referenced this pull request Nov 6, 2023
…276-on-v3.8.x

Backport PR #27276 on branch v3.8.x (Clarify behavior of `prune` parameter to MaxNLocator.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: prune parameter of MaxNLocator has no effect
3 participants