Re: [Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale

On 12 June 2017 at 10:05, Martin (gzlist) via Python-Dev wrote: > I don't like the side effect of changing the standard stream error > handler to surrogateescape if LANG=C.UTF-8 is actually set. Obviously > bad data vs exception is a trade off anyway, but means to get a

Re: [Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale

On 09/05/2017, Nick Coghlan wrote: > > Enough changes have accumulated in PEP 538 since the start of the > previous thread that it seems sensible to me to start a new thread > specifically covering the current design (which aims to address all > the concerns raised in the

Re: [Python-Dev] Remove embedded expat library?

> On 11 Jun 2017, at 12:10, Victor Stinner wrote: > > Le 11 juin 2017 09:38, "Ronald Oussoren" > a écrit : > I don’t think it would be a good idea to rely on the system provided libexpat > on macOS, as Apple is

Re: [Python-Dev] Remove embedded expat library?

Le 11 juin 2017 09:38, "Ronald Oussoren" a écrit : I don’t think it would be a good idea to rely on the system provided libexpat on macOS, as Apple is not exactly fast w.r.t. upgrading their external dependencies and could easily stop updating libraries when the no longer

Re: [Python-Dev] Remove embedded expat library?

> On 9 Jun 2017, at 18:03, Ned Deily wrote: > > On Jun 9, 2017, at 08:43, Victor Stinner wrote: > >> I expect that all Linux distributions build Python using >> --with-system-expat. It may become the default? What about macOS and >> other operating