On 15 December 2016 at 23:19, Toshio Kuratomi <a.badger(a)gmail.com> wrote:
The costs here are very steep in both directions... so I don't
see any
good ways to address it yet. The best I can offer so far is for the
library to check and warn if an ascii-only locale is used. That way
someone who encounters a UnicodeError in code deployed under mod_wsgi
is shown how to debug this when they run it under /usr/bin/python. So
something like this from the library:
libpython detected LC_CTYPE=C.Some encoding errors may occur..
Use.PYTHONALLOWCLOCALE=1 LC_CTYPE=C /usr/bin/python if debugging this
under /usr/bin/python.
OK, I've posted a summary at
https://bugzilla.redhat.com/show_bug.cgi?id=1404918#c5 with some
proposed wording for the error messages.
For the embedded runtime warning, I'm suggesting "Some libraries and
operating system interfaces may not work correctly." but could be
pretty easily talked into changing that to "Some text encoding related
errors may occur." (as even if a library bails out the way click does,
it will probably mention ASCII in the error message)
For the PYTHONALLOWCLOCALE case I'm suggesting "Some libraries,
applications and operating system interfaces may not work correctly."
as that's literally the answer to "Why isn't the C locale allowed by
default anymore?".
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia