docs: clarify markevery float spacing - #31664
Merged
Merged
Conversation
timhoffm
approved these changes
May 13, 2026
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
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
Closes #27842.
Clarify the
Line2D.set_markeverydocstring for floatmarkeveryvalues. The updated wording explains that the ideal spacing is measured along the drawn line and then coerced to the nearest data point, so jagged lines may not appear evenly spaced along the x- or y-axis.Validation:
python -m py_compile lib\matplotlib\lines.pygit diff --checklib/matplotlib/lines.pywithastto confirm the updatedLine2D.set_markeverydocstring contains the new wording.AI Disclosure
I used Codex locally to help identify the issue, draft the wording, and run validation. I reviewed the final one-file diff before opening this PR.
PR checklist
markevery[float]considers path length along drawn line #27842" is in the body of the PR description to link the related issuepy_compile,git diff --check, and an AST docstring check