gh-133967: Do not normalize locale name 'C.UTF-8' to 'en_US.UTF-8'#135347
gh-133967: Do not normalize locale name 'C.UTF-8' to 'en_US.UTF-8'#135347Yhg1s merged 1 commit intopython:mainfrom
Conversation
|
Note that we have had the 'c.utf8' mapping for a long time in the past (Python 3.4 - 3.11). It was changed to map to 'C.UTF-8' in Python 3.12. With the PR, the mapping will be removed again, but the normalization will still go from 'c.utf8' to 'C.UTF-8', just via a different code path. For consistency and to make this a bug fix, rather than a new feature, it's probably better to keep the 'c.utf8' -> 'C.UTF-8' mapping in the table and enforce this, but I'll leave that for you to decide. |
|
See #14925 for some additional context. |
|
Thanks @serhiy-storchaka for the PR, and @Yhg1s for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
…-8' (pythonGH-135347) (cherry picked from commit 0f866cb) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
GH-135349 is a backport of this pull request to the 3.14 branch. |
…-8' (pythonGH-135347) (cherry picked from commit 0f866cb) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
GH-135350 is a backport of this pull request to the 3.13 branch. |
|
|
@malemburg auto-merge went through before anyone could address your comment, I think. Do you think it's worth making that change in a follow-up? |
It would be good to readd the mapping to the table, since this will get added back in the next run of the Tools/i18n/makelocalealias.py tool anyway and could then cause questions popping up, since Sergey added the comment to the table saying that the mapping was removed. |
Uh oh!
There was an error while loading. Please reload this page.