Thanks,@serhiy-storchaka

Some of the edits made by the script are a bit odd. E.g. "de_li.utf8" is being removed, even though the original file still lists it:https://gitlab.freedesktop.org/xorg/lib/libx11/-/blob/master/nls/locale.alias.pre?ref_type=heads#L266

This is because "de_li" was added. The mapping does not contain all data fromlocale.alias if it can safely be derived.normalize() takes the mapping for "de_li" ("de_LI.ISO8859-1") and replaces encoding "ISO8859-1" with "utf8". It makes the mapping twice or more less.

Ah, yes, you're right.

Thanks@serhiy-storchaka for the PR, and@malemburg for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

GH-129658 is a backport of this pull request to the3.13 branch.

Thanks,@serhiy-storchaka

Thanks for merging, but please don't forget to edit commit messages.

I haven't done this in CPython in a longer while. Can you point me to documentation about the needed edits ?

I found this reference:https://devguide.python.org/getting-started/git-boot-camp/#accepting-and-merging-a-pull-request and it appears you are referring to the changing the way Github issues and PRs are referenced (using "GH-" instead of "#").

No, I meant that since the NEWS file was added in a separate commit, GitHub combined commit messages of several commit in a commit message of the merged commit. Seef61afca. It contains a duplicate of the title of the original commit message and the commit message of the following commit. In worst cases (e.g.4f82621) it can contain tens of useless lines that reflect the history of editing the PR, and not its final form. This is why we need to edit commit message before confirming merging.

Ah, ok, I see. Yes, I should have taken a closer look before hitting merge. Will do next time.