On 8 January 2017 at 02:47, Stephen J. Turnbull
wrote:
> I agree that people around me mostly know only two encodings: "works
> for me" and "mojibake", but they also use locales configured for them
> by technical staff. On top of that, international students (the most
> likely victims of "UTF-8 b
INADA Naoki writes:
> I want UTF-8 mode is enabled by default (opt-out option) even if
> locale is not POSIX,
> like `PYTHONLEGACYWINDOWSFSENCODING`.
>
> Users depends on locale know what locale is and how to configure it.
> They can understand difference between locale mode and UTF-8 mode
Hi folks,
Many of you would have seen Victor's recent PEP proposing the
introduction a new "UTF-8" mode that told Python to use UTF-8 by
default in the legacy C locale (similar to the way CPython behaves on
Mac OS X, Android and iOS), as well as allowing explicit selection of
that mode regardless
2016-12-31 16:42 GMT+09:00 Nick Coghlan :
> On 31 December 2016 at 08:24, Masayuki YAMAMOTO > wrote:
>
>> I have read the discussion and I'm sure that use structure as Py_tss_t
>> instead of platform-specific data type. Just as Steve said that Py_tss_t
>> should be genuinely treated as an opaque