Skip to content

Conversation

@timhoffm
Copy link
Member

Closes #27190.

Note: I've left out the part on adding something to the coding guidelines. The combination of the explanations in pyplot.py and boilerplate.py should be good enough to understand how this works. And the test test_pyplot_up_to_date should notify any need to run boilerplate.py.
I would treat this mechanism as an implementation detail that uncovers itself when needed. Adding to the coding guidelines only bloats them, but 95% of contributors will not have to know about it because they don't change our public API.

@story645
Copy link
Member

but 95% of contributors will not have to know about it because they don't change our public API

Then what about adding a note in the API changes guide?

Copy link
Member

@story645 story645 left a comment

Choose a reason for hiding this comment

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

Thanks for doing this! Minor grammar fixes and style changes.

Copy link
Member

@story645 story645 left a comment

Choose a reason for hiding this comment

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

This is definitely an improvement, thanks!

I'd still prefer an additional note/mention in the API changes docs, but maybe in a follow up cause the where may be not obvious?

@timhoffm timhoffm added this to the v3.11.0 milestone Sep 17, 2025
@timhoffm timhoffm merged commit 01cfcb0 into matplotlib:main Sep 17, 2025
38 of 40 checks passed
@timhoffm timhoffm deleted the doc-boilerplate branch September 17, 2025 05:22
@timhoffm
Copy link
Member Author

@story645 I’ll leave any potential follow up to you.

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.

[Doc]: clarify when and how to use boilerplate.py

3 participants