-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
DOC: improve description of boilerplate.py #30562
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
Conversation
8f78b99 to
9571737
Compare
Then what about adding a note in the API changes guide? |
story645
left a comment
There was a problem hiding this 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.
9571737 to
49df95b
Compare
49df95b to
c85328a
Compare
story645
left a comment
There was a problem hiding this 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?
|
@story645 I’ll leave any potential follow up to you. |
Closes #27190.
Note: I've left out the part on adding something to the coding guidelines. The combination of the explanations in
pyplot.pyandboilerplate.pyshould be good enough to understand how this works. And the testtest_pyplot_up_to_dateshould notify any need to runboilerplate.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.