-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Improve documentation for examples/widgets/textbox.py #16549
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
Improve documentation for examples/widgets/textbox.py #16549
Conversation
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 the contribution!
Please do not leave trailing whitespace. Our style checker does not like that:
./examples/widgets/textbox.py:8:75: W291 trailing whitespace
./examples/widgets/textbox.py:9:79: W291 trailing whitespace
./examples/widgets/textbox.py:12:30: W291 trailing whitespace
./examples/widgets/textbox.py:13:39: W291 trailing whitespace
./examples/widgets/textbox.py:29:76: W291 trailing whitespace
./examples/widgets/textbox.py:31:23: W291 trailing whitespace
I don't see any specific error in the failed CI... help is appreciated! |
For travis, click on the failed job (flake8 in this case) and inspect the log:
You can ignore failures in the nightly build. Similarly, for CircleCI (which we use for doc-building), click on the failed job. Check the messages in the "Build documentation" section. Usually, it's a good idea to download that log and search for "WARNING" with a text editor. This gives:
|
Those are probably my fault 'cause I didn't properly format my snippet in rest. the guidelines are here: https://matplotlib.org/devel/documenting_mpl.html#writing-docstrings Optimally |
@timhoffm I did download the circleci log but I only searched for |
Reading that warning message again, looks like To fix the warnings, I think the following replacements should work:
|
@story645 following that guideline you sent, I figured out the right way to do it. It has to be
|
The new commit addressed all failures and I think it's ready to merge |
Thanks for your contribution! 🚀 |
PR Summary
The current documentation in textbox.py doesn't explicitly explain that this is an interactive GUI. Its name textbox may be easily confused with normal text with box, which is probably used more often. And it's hard to tell otherwise from the embedded screenshot. It fooled me for a good minute at least. I added a few notes in docstring and comment to stress the fact that this is different than just inserting a static text box. Also to bring more clarity to the purpose of the "submit" function.
This PR is also related to #11654
PR Checklist