@merwok: Please replace # with GH- in the commit message next time. Thanks!

Thanks @merwok for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8.
🐍🍒⛏🤖

Sorry, @merwok, I could not cleanly backport this to 3.8 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker dd1a20f324d88f4171aca480b7972d68cab212c5 3.8

Sorry @merwok, I had trouble checking out the 3.7 backport branch.
Please backport using cherry_picker on command line.
cherry_picker dd1a20f324d88f4171aca480b7972d68cab212c5 3.7

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

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

Thanks for review. If the problem comes again, we could add a comment at the end of the file.

Nice idea about a comment at the end of the file!

Sorry, being the latest entry added by myself I read the sorted nature of the file at the top but didn't that it was sorted by last name expecting sorted by first name. It's a good idea to add the comment in the end about the same. I tried adding a check to patchcheck.py since it already has a check for ACKs update to ensure the file stays sorted but hit some cases with unicode names having different value.

Thanks.

The order is not 100% exact, so I think trying to make an automated order would be hard (e.g. if there are three bits in the name, could be two first names or a two-part last name).

Let me make a PR to add the comment at the end and add it to the backports PRs too (and please review these!)