On 12 June 2017 at 22:24, Nick Coghlan wrote:
> On 12 June 2017 at 18:56, Victor Stinner wrote:
>> Hi,
>>
>> Nick Coghlan pushed his implementation of his PEP 538: nice! Nice step
>> forward to UTF-8 everywhere ;-)
>>
>> I would prefer to not be annoyed by warning messages about encodings
>> at s
On 6/25/2017 8:14 AM, Terry Reedy wrote:
On 6/12/2017 4:30 PM, Glenn Linderman wrote:
On 6/12/2017 1:11 PM, Terry Reedy wrote:
I do not have any locale-related env vars. You should check whether
the warning is off on all Win10 systems, as well as Win7 and Win8.
Many Windows users know nothin
On 6/12/2017 4:30 PM, Glenn Linderman wrote:
On 6/12/2017 1:11 PM, Terry Reedy wrote:
I do not have any locale-related env vars. You should check whether
the warning is off on all Win10 systems, as well as Win7 and Win8.
Many Windows users know nothing about ENV VARS, and even if they do,
th
On 13 June 2017 at 19:48, Victor Stinner wrote:
> While I'm not opposed to PYTHONCOERCECLOCALE=warn, I'm not sure that
> *developers* will use it. Usually, developers don't care of Unicode
> until enough users complain that their application don't work on a
> specific configuration on a specific p
On 13 June 2017 at 19:07, Victor Stinner wrote:
> Ok, if you want to have a more concrete example of regression
> introduced by this warning, look at test_tracemalloc failures on this
> FreeBSD buildbot:
> http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Debug%203.x/builds/419/s
2017-06-13 8:51 GMT+02:00 Nick Coghlan :
> If we turned the warning off by default, but retained an easy
> "on-switch" for the warning to help track places where locale coercion
> is triggering unexpectedly (e.g. "PYTHONCOERCECLOCALE=warn"), that
> would probably give us the best of both worlds.
H
Ok, if you want to have a more concrete example of regression
introduced by this warning, look at test_tracemalloc failures on this
FreeBSD buildbot:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Debug%203.x/builds/419/steps/test/logs/stdio
I expect that a *lot* of tests usin
On 13 June 2017 at 06:58, Gregory P. Smith wrote:
> I guess so. It is a system environment configuration problem. But I'd still
> imagine that end users never touch their LANG or LC_* environment variables
> themselves. (the only time I touch anything is to explicitly set LANG=C on
> occasion whe
On Mon, Jun 12, 2017 at 1:48 PM Nathaniel Smith wrote:
> On Jun 12, 2017 10:50, "Gregory P. Smith" wrote:
>
>
> The problem, as with all warnings, is that it isn't the user who has
> control over the problem who sees the warning. It is the end use of an
> application on a system that sees it.
>
On Jun 12, 2017 10:50, "Gregory P. Smith" wrote:
The problem, as with all warnings, is that it isn't the user who has
control over the problem who sees the warning. It is the end use of an
application on a system that sees it.
I don't think I understand the distinction you're making here. This
On 6/12/2017 1:11 PM, Terry Reedy wrote:
I do not have any locale-related env vars. You should check whether
the warning is off on all Win10 systems, as well as Win7 and Win8.
Many Windows users know nothing about ENV VARS, and even if they do,
they may not know how (I don't know the details)
On 12 June 2017 at 21:11, Terry Reedy wrote:
> I do not see this with my fresh 3.7 repository debug build on my Win 10
> machine. If I did, I would be -1000. This warning should be treated
> as a deprecation warning, off by default.
My understanding is that this is a Unix-only change. If it aff
On 6/12/2017 5:35 AM, INADA Naoki wrote:
On Mon, Jun 12, 2017 at 5:56 PM, Victor Stinner
wrote:
Hi,
Nick Coghlan pushed his implementation of his PEP 538: nice! Nice step
forward to UTF-8 everywhere ;-)
I would prefer to not be annoyed by warning messages about encodings
at startup if possibl
>> -1 for disable coercion by default: It's too unhelpful for beginners.
>
> Are you proposing to reject the PEP that you approved? Now I'm confused.
>
No, I just wanted to clarify your propose.
You said "I'm able to render my hello world with the wrong locale :-)".
So I want to clarify you didn
On Mon, Jun 12, 2017 at 5:25 AM Nick Coghlan wrote:
> On 12 June 2017 at 18:56, Victor Stinner wrote:
> > Hi,
> >
> > Nick Coghlan pushed his implementation of his PEP 538: nice! Nice step
> > forward to UTF-8 everywhere ;-)
> >
> > I would prefer to not be annoyed by warning messages about enco
On 06/12/2017 05:24 AM, Nick Coghlan wrote:
I suspect the eventual outcome is going to be dropping that particular
warning (since it's been problematic for Fedora's 3.6 backport as
well, and the problems are due to the warning itself, *not* the locale
coercion), but I'd prefer to keep the notifi
2017-06-12 15:28 GMT+02:00 INADA Naoki :
>> I like using LANG=C to display a manual page in english.
>
> Me too. But we can use LC_CTYPE=C.UTF-8 with LANG=C.
My point is that LANG=C is easy to remember and "it just works".
> And LC_CTYPE=C.UTF-8 is much easier (and ideal) than
> PYTHONLOCALECOER
On Mon, Jun 12, 2017 at 6:46 PM, Victor Stinner
wrote:
> 2017-06-12 11:35 GMT+02:00 INADA Naoki :
>> I think "Good practice" is set `LC_CTYPE=C.UTF-8` environment variable,
>> as warning says.
>
> I like using LANG=C to display a manual page in english.
Me too. But we can use LC_CTYPE=C.UTF-8 wi
On 12 June 2017 at 14:24, Nick Coghlan wrote:
> On 12 June 2017 at 18:56, Victor Stinner wrote:
>> Hi,
>>
>> Nick Coghlan pushed his implementation of his PEP 538: nice! Nice step
>> forward to UTF-8 everywhere ;-)
>>
>> I would prefer to not be annoyed by warning messages about encodings
>> at s
On 12 June 2017 at 18:56, Victor Stinner wrote:
> Hi,
>
> Nick Coghlan pushed his implementation of his PEP 538: nice! Nice step
> forward to UTF-8 everywhere ;-)
>
> I would prefer to not be annoyed by warning messages about encodings
> at startup if possible:
>
> "Python detected LC_CTYPE=C: LC_
2017-06-12 11:35 GMT+02:00 INADA Naoki :
> I think "Good practice" is set `LC_CTYPE=C.UTF-8` environment variable,
> as warning says.
I like using LANG=C to display a manual page in english. Technically,
I know that it's wrong, but it works. I don't see the point of the
warning. I'm able to render
On Mon, Jun 12, 2017 at 5:56 PM, Victor Stinner
wrote:
> Hi,
>
> Nick Coghlan pushed his implementation of his PEP 538: nice! Nice step
> forward to UTF-8 everywhere ;-)
>
> I would prefer to not be annoyed by warning messages about encodings
> at startup if possible:
>
> "Python detected LC_CTYPE
On Mon, 12 Jun 2017 10:56:31 +0200
Victor Stinner wrote:
> Hi,
>
> Nick Coghlan pushed his implementation of his PEP 538: nice! Nice step
> forward to UTF-8 everywhere ;-)
>
> I would prefer to not be annoyed by warning messages about encodings
> at startup if possible:
>
> "Python detected LC_
23 matches
Mail list logo
