@willingc If you have some time, could you also review this one?

Hi @maggyero. Would you please resubmit this PR without the whitespace changes? It's acceptable to have one or two spaces following a period. It helps a reviewer save time if only the typo corrections or text changes are submitted in a PR. Thanks!

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

Hi @willingc. Thank you for looking at this. Single and double spaces were mixed in this file, that is why I normalized them in my last commit in the first place. But you are right, it is harder to review when there are other corrections involved in the PR, so I reverted them.

I have made the requested changes; please review again.

Thanks for making the requested changes!

@willingc: please review the changes made to this pull request.

@maggyero Travis is reporting errors in linting

[1] library/codecs.rst:845: OMG TABS!!!1
1 problem with severity 1 found.

Please review and update. Once Travis is green for all checks, please ping me again.

@willingc Thanks, fixed. I have made the requested changes; please review again.

Thanks for making the requested changes!

@willingc: please review the changes made to this pull request.

Thanks for reviewing this @willingc. Could we also backport this PR to the 3.7 and 3.8 branches?

Could you backport this PR to the 3.7 and 3.8 branches?
I have another PR #15732 base on this PR.

@willingc

Thanks @maggyero for the PR, and @willingc for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖

Sorry @maggyero and @willingc, I had trouble checking out the 3.7 backport branch.
Please backport using cherry_picker on command line.
cherry_picker 891e9e3b44c99d643dc309a4e63082451271b136 3.7

About to board a flight. If anyone wishes to cherry-pick this, that would be great. Otherwise, it will need to wait until tomorrow.

No hurry, take your time.
It doesn't matter even next week.

Hi @willingc. May I request your time to finalize the backport to Python 3.7 and to add the backport label for Python 3.8?

Thanks @maggyero for the PR, and @willingc for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖

I'm having trouble backporting to 3.7. Reason: 'Error 110 while writing to socket. Connection timed out.'. Please retry by removing and re-adding the needs backport to 3.7 label.

Thanks @maggyero for the PR, and @willingc for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖

GH-16524 is a backport of this pull request to the 3.7 branch.

Thanks @maggyero for the PR, and @willingc for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8.
🐍🍒⛏🤖

GH-16526 is a backport of this pull request to the 3.8 branch.

Thanks @JulienPalard for backporting this.