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
bpo-34906: Doc: Fix typos (2) #9735
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.
LGTM. You'll probably need to make a manual backport to 3.7 and 3.6 of the subsets that apply to each.
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 idlelib corrections will backport cleanly.
@vadmium here is my patch for |
For this PR and the previous one, I used |
@ned-deily if you want, I can do the PR for 3.7 & 3.6, just keep me informed and I will work on it asap. |
Please go ahead with backports. I would first try using cherry_picker to make a 3.7 patch to see how many merge conflicts need to be resolved. For 3.6, I believe I would try cherry-picking the 3.7 patch, as the 3.6 subset will be a subset of the 3.7 subset. (This is not the usual procedure.) |
Ste'phane, are you planning to backport? If not, I will do so for a couple of IDLE changes. |
Fix typos (cherry picked from commit 683281f)
Second turn for the typo in the doc, mainly for the Misc/ directory
https://bugs.python.org/issue34906