Message55067
this came up on #ubuntu-devel; Debian and Ubuntu do not generate all libc locales by default, so it is likely that
$ LC_ALL=en_US.UTF-8 python -c "import locale; locale.setlocale(locale.LC_ALL, '')"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python2.5/locale.py", line 476, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting
fails on a system (often experienced ssh'ing into a server system where your current locale doesn't exist). Examples for bug reports in various applications are:
https://launchpad.net/bugs/91583 (apt-listchanges)
https://launchpad.net/bugs/88638 (pitivi)
https://launchpad.net/bugs/81556 (exaile)
https://launchpad.net/bugs/90525 (hwdb-client)
In C, the result of the setlocale(3) call can be, and usually is ignored, if the locale cannot be set.
It is argued that the Python interface for locale.setlocale() should not raise an exception by default, if the locale is missing on the system.
That would be an behaviour change of locale.setlocale(), so the original behavour should be kept as an option (introducing an optional third parameter to raise the exception when the locale doesn't exist). Is this an appropriate change, or could another change be suggested?
|
|
Date |
User |
Action |
Args |
2007-08-23 16:12:44 | admin | link | issue1703592 messages |
2007-08-23 16:12:44 | admin | create | |
|