-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Add Sphinx spell check extension for docs #5356
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
| fallback | ||
| genericity | ||
| indices | ||
| ing |
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 for ”await-ing” in
mypy/docs/source/more_types.rst
Line 576 in f5058bc
| expect to get back when ``await``-ing the coroutine. |
Which is a bit weird, and showcases the downside that the dictionary file would be need to be continuously maintained and updated.
|
FWIW I don’t believe in batch spell checking. IMO it’s up to the text editor. But it’s Jukka’s docs so maybe he likes it? |
|
If we do go ahead with this, it would be a good idea to add it to CI, so that we are all using it consistently. |
Yes, that would be the way to go, but I worry that we'd end up constantly updating the dictionary to teach it about words like unparameterized or unannotated... |
I'm not particularly worried about that actually. 2000 or so words make up about 80% of all words used in a day. I expect for a technical document that is likely a lower percentage, but I don't think that much new vocabulary will be introduced. Of course, we can always try this, and if we find it annoying, rip it out. |
|
Any final thoughts on the general idea, or should we just close this PR for now given the low traction? |
I think we are waiting on @JukkaL to give an opinion. I don't see a problem with leaving this open for a while, unless you would like to withdraw this PR, in which case it is of course your prerogative to close it if you wish. |
|
This seems like a reasonable idea to me -- we've had a lot of spelling mistakes, and catching them all without some automation is hard. If this turns out to be too noisy, we can turn this off. I'll play around with this a bit before merging (this might have to wait for a few weeks, since I'm going to be on vacation). |
There's been a number of misspelled words in the documentation. This PR adds the ability to spell check the documentation via a make target.
Spell checking is implemented by adding a Sphinx spell check extension: http://sphinxcontrib-spelling.readthedocs.io/en/latest/
We use a dictionary file which contains words that are known to be spelled correctly, such as "mypy" and "Dataclasses".
Sample output:
The two misspelled words reported in the output are fixed in #5355
What do you think?