Recently, tirkarthi (xtreak) works on finding and fixing typos.
And I (18z) came up with the idea of creating a spellcheck bot to improve
the quality of cpython.
We had discussion in https://github.com/python/cpython/pull/13749
And it is summarized below:
Reducing typo in a constructive way.
To be Solved:
Even after reducing the code checked, there will still be mostly false
High frequency of updating dictionary.txt (false positive typo).
Interfacing the filter with aspell to get some numbers.
The report could be made optional with a spellcheck label.
Code for reducing .py files to strings and comments.
Command line for spellcheck.
There are problems to be solved.
But I think we can always find a better solution.
So, I’ll be working on interfacing the filter with aspell to get some
Looking forward to hearing more opinions. :D
(cross posting to python-committers, python-dev, core-workflow)
PEP 581: Using GitHub Issues has been accepted by the steering council, but
PEP 588: GitHub Issues Migration plan is still in progress.
I'd like to hear from core developers as well as heavy b.p.o users, the
1. what features do they find lacking from GitHub issues, or
2. what are the things you can do in b.p.o but not in GitHub, or
3. Other workflow that will be blocked if we were to switch to GitHub
By understanding your needs, we can be better prepared for the migration,
and we can start looking for solutions.
In addition, I received tip that the GitHub team is very motivated to help
us, and if we can give them some of our most wanted features, they *might* be
able to accommodate us. But first we need to tell them what we need.
They're not promising anything, but I'd like to at least try and give them
1. Please leave your comment in this issue:
2. Leave your +1 by reacting 👍 to suggested feature by others
3. Please do this before October 1, 2019 (not a hard deadline)