[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-17 Thread Nick Coghlan
Nick Coghlan added the comment: OK, PEP 538 is effectively disabled on FreeBSD and Mac OS X now, and the locale coercion and compatibility warnings are off by default everywhere. PYTHONCOERCECLOCALE=warn is explicitly documented as a debugging tool for use when folks already suspect that

[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-17 Thread Nick Coghlan
Nick Coghlan added the comment: New changeset eb81795d7d3a8c898fa89a376d63fc3bbfb9a081 by Nick Coghlan in branch 'master': bpo-30565: Add PYTHONCOERCECLOCALE=warn runtime flag (GH-2260) https://github.com/python/cpython/commit/eb81795d7d3a8c898fa89a376d63fc3bbfb9a081 --

[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-17 Thread Nick Coghlan
Nick Coghlan added the comment: OK, based on the latest round of custom buildbot results (e.g. http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Debug%20custom/builds/12/steps/test/logs/stdio ), it looks like the main remaining problems are those covered by issue 30672,

[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-17 Thread STINNER Victor
STINNER Victor added the comment: As I wrote on python-dev, I would prefer no warning and no option to enable warnings. But it's not my PEP, I would prefer that Nick makes a choice here. Right now, my main worry is that my little (freebsd) buildbots are still sick --

[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-17 Thread Nick Coghlan
Nick Coghlan added the comment: By having the warnings always compiled in, but off by default, "PYTHONCOERCECLOCALE=warn" becomes a debugging tool for integration failures that we (or end users) suspect might be due to the locale coercion behaviour. It's essentially an even more esoteric

[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-17 Thread INADA Naoki
INADA Naoki added the comment: If this warnings are disabled by default, who enable it? How about just remove them? I'm OK to remove them all. Since it's not ideal, nothing go worse than Python 3.6. Additionally, if PEP 540 is accepted, we can use UTF-8 for stdio and filesystem encoding even

[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-17 Thread Nick Coghlan
Changes by Nick Coghlan : -- pull_requests: +2310 ___ Python tracker ___ ___

[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-16 Thread Nick Coghlan
Changes by Nick Coghlan : -- nosy: +inada.naoki ___ Python tracker ___ ___

[issue30565] PEP 538: silence locale coercion and compatibility warnings by default?

2017-06-15 Thread Nick Coghlan
Nick Coghlan added the comment: Updated issue title to reflect the fact we're now considering just silencing *all* the warnings by default. -- title: PEP 538: default to skipping warning for implicit locale coercion? -> PEP 538: silence locale coercion and compatibility warnings by