-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix spelling errors #22964
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
Fix spelling errors #22964
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.
Thank you for opening your first PR into Matplotlib!
If you have not heard from us in a while, please feel free to ping @matplotlib/developers
or anyone who has commented on the PR. Most of our reviewers are volunteers and sometimes things fall through the cracks.
You can also join us on gitter for real-time discussion.
For details on testing, writing docs, and our review process, please see the developer guide
We strive to be a welcoming and open project. Please follow our Code of Conduct.
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.
The vast majority of spelling corrections were suggested by Google Sheets.
All fault is mine
When iterating over the contents of the the dynamically generated proxy lists | ||
When iterating over the contents of the dynamically generated proxy lists |
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 isn't technically a misspelling. I'm moderately confident in the word undoublings I've made, but I've only recently started performing this additional change...
Removed definct set_measurement in wx toolbar | ||
Removed defunct set_measurement in wx toolbar |
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.
?
``dt = np.datetim64(e*1e6, 'us')``. | ||
``dt = np.datetime64(e*1e6, 'us')``. |
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.
probably?
See the Ananconda web page for installation support. | ||
See the Anaconda web page for installation support. |
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.
Brand
* module by dlsym() only if it is really located in the given modile, | ||
* module by dlsym() only if it is really located in the given module, |
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.
probably
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 helping to improve Matplotlib!
I suggest to squash all changes into a single commit "Fix spelling errors" when all is sorted out.
Changed the fmt kwarg of errorbar to support the the mpl convention that | ||
Changed the fmt kwarg of errorbar to support the mpl convention that |
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.
Fixing spelling errors in changelogs is ok.
5484da1
to
cfe8032
Compare
It is interesting that this found so many more issues than codespell in #22777. Is there a reference for what the difference is with this approach versus codespell? I'd additionally suggest that major spelling updates and other formatting changes get added to the blame ignore file once squashed down to one commit: https://github.com/matplotlib/matplotlib/blob/main/.git-blame-ignore-revs |
codespell has different design goals. It targets common misspellings made by programmers. check-spelling is domain agnostic (although it doesn't really support languages other than English) in that it would be just as happy to work on a document destined for a scientific journal or someone's script for a theater production. "All" it does is parse text looking for words and then check them against the configured dictionaries. I personally take that output and then ask Google (Sheets) to suggest word corrections. Google has a much larger sense of corrections than the average person. -- I use the to generate commits and iterate through the tooling. I hide that iteration from projects in an ancillary fork, but you can see the steps https://github.com/check-spelling/matplotlib/actions if you're curious. As I'm looking through the spreadsheet of words with Google Sheets, if something jumps out at me, I'll correct that was well, or as I look at a correction as applied and spot something else, I might fix that too. "All" is a vast simplification, check spelling has a number of heuristics for various things including detecting files to ignore, supplemental patterns to detect, suggesting supplemental dictionaries to use, ... So far I haven't looked into building a table of automatic corrections a la codespell, although I do have notes in forbidden patterns to explain to a reader why a pattern might trip. But I know that a number of people have responded to my PRs by suggesting additions to codespell. |
It looks like this project uses merges, which means I should be able to squash the spelling fixes and then add a second commit that updates the blame ignore revs file. I'll do that once people tell me they're happy with the changes. |
Moved to draft until the comments above are dealt with and the rebase is done. |
I am happy with the changes, so please go ahead and rebase and add the git blame-stuff. |
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.
Looks good to me. There are a few additional mistakes caught by @QuLogic that would be good to address as well. In particular, the note about keeping the previous "bad" spelling in the changelog.
I don't think the issues brought up by @QuLogic have been addressed - moved back to draft |
Thanks @jsoref and congratulations on your first contribution to Matplotlib! We hope to see you back. |
PR Summary
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at jsoref@5ccdace#commitcomment-72743863
The action reports that the changes in this PR would make it happy: jsoref@d4a8b5d
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
Spelling errors can often mask bugs. User facing errors also hinder the user experience.
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).