On Tue, Jan 26, 2016 at 11:29:07AM +1100, Brian May wrote: > python3-click has checks to ensure it is called with a non-ASCII > locale. Or if it is an ASCII locale, it raises a fatal error. Or at > least it tries to raise a fatal error. [...] > The problem is that when building djangorestframework, I need to have a > utf8 locale available. C.UTF-8 is fine. However, I don't think there is > any guarantee (??) that a utf8 locale will be available when building > packages. This I believe is the root cause of #812672. > > So should I somehow be trying to get the UTF-8 locale (is this possible > from debian/rules?)
C.UTF-8 is always available on Debian since a long time ago, precisely to be a guaranteed UTF-8 locale. It's included in the libc-bin package which is Essential:yes. My guess as to the cause of #812672 is that you have LC_CTYPE or LC_ALL set to an ancient locale. These variables override LANG, the order is LC_ALL>LC_CTYPE>LANG. > should I submit another bug report against > python3-click saying that it really should work in ASCII environments? My personal preference would be to drop support for non-UTF8 locales as soon as possible. They're a heap of work; that effort could be better spent fixing remaining problems in UTF-8 locales. -- A tit a day keeps the vet away.
