update locale aliases for glibc 2.24 #422
This change needs an entry in Misc/NEWS. Please open an issue on the tracker for discussion and reference.
| data.update(parse(args.locale_alias)) | ||
| + data.update(parse_glibc_supported(args.glibc_supported)) |
Because some of the X11 locale aliases conflict with the glibc ones. glibc obviously uses the glibc ones. This fixes problems where we would return encodings (like en_IN.ISO8859-1) that don't correspond to the C-level one.
This is separate issue (bpo-20087). Let don't mix updating to newer glibc with changing the priority of aliases tables. The latter change needs blessing from the module maintainer.
IMO, this is the only interesting change. I only upgraded the alias list because finding an old version of glibc is slightly annoying and updating it is unlikely to break things.
|
I suppose some of changes are related to bpo-20087. This was not discussed yet. |
|
I think this is the correct fix for bpo-29571. |
|
Aye, I never did figure out why +1 for fixing the underlying discrepancy in 3.7+. |
|
@benjaminp, when you run
It should be added to the long comment before the alias table. Only "updated" lines are needed, not "removed". Add a comment that glibc aliases now are preferred. This is the main cause of changes. And please add a test for en_IN. |
|
Please see the ticket for discussion: http://bugs.python.org/issue20087 |
|
This merge should be undone. The PR clearly contains bugs and also is not complete. See the ticket for discussion. |
I also made makelocalealias.py prefer the glibc defaults.