[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: I don't see any test_warnings anymore on http://code.google.com/p/bbreport/wiki/PythonBuildbotReport. Close this issue. -- status: open -> closed ___ Python tracker __

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: > Still happens with r84709 on PPC Tiger 3.x It's not the same error, PYTHONWARNINGS is decoded from the wrong encoding: locale encodind instead of utf-8. r84731 should fix this bug (at least, it restores the encoding used because my last commit, r84694). Wi

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Florent Xicluna added the comment: Still happens with r84709 on PPC Tiger 3.x == FAIL: test_nonascii (test.test_warnings.CEnvironmentVariableTests) -- Traceba

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: It should be fixed by r84694. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: I know test_warnings failure and I will try to fix it soon. -- ___ Python tracker ___ ___ Python-bug

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Changes by Florent Xicluna : -- keywords: +buildbot ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Florent Xicluna added the comment: There's a failure on the same buildbot, "x86 debian parallel", with test test_subprocess (test_undecodable_env). This test was introduced with issue #8391. The test_subprocess and test_warnings failures are specific to this buildbot. -- ___

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Florent Xicluna added the comment: A similar issue occurs on "x86 debian parallel" buildbot: == FAIL: test_nonascii (test.test_warnings.CEnvironmentVariableTests)

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: Oh, Python 3.1 doesn't use the PYTHONWARNINGS variable: commit blocked in 3.1 (r81362). -- dependencies: -regrtest: use backslashreplace error handler for stdout status: pending -> closed ___ Python tracker

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Changes by STINNER Victor : -- resolution: -> fixed status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: Ok, I commited my patch: r81358 (py3k). I'm waiting for the buildbots before backporting the fix to 3.1. -- ___ Python tracker ___

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: tarek tested on Mac OS X: the patch fixes test_warnings issue. -- ___ Python tracker ___ ___ Python-

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: Attached patch creates PySys_AddWarnOptionUnicode() function and decodes PYTHONWARNINGS variable with the file system encoding (as it is done for os.environ, to be consistent) instead of the locale encoding. The patch only concerns the POSIX version. Windows

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: os.environ is decoded with sys.getfilesystemencoding(), whereas PYTHONWARNINGS is decoded with the locale encoding (locale.getpreferredencoding()) :-/ -- ___ Python tracker __

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: The test was introduced by r80066 (issue #7301). -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: Does my fix this #8533 fixes this issue or not? I guess yes, but I would prefer a confirmation. -- ___ Python tracker ___ _

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

STINNER Victor added the comment: The bug only occurs on Mac OS X because file system encoding is hardcoded to UTF-8 on this OS and the test is skipped if the file system encoding is ASCII. But the bug is not specific to test_warnings, as mentionned by R. David Murray: #8533 is the real bug.

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Michael Foord added the comment: What does issue 8522 have to do with it - did you mean a different issue? In unittest it could catch the UnicodeEncodeError and write the ascii repr instead. -- ___ Python tracker

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

R. David Murray added the comment: Victor has proposed a patch for the traceback problem for regrtest, I think. I haven't looked at it, but I wonder if there is something that can instead be done to make unittest work in cases like this when run in an ascii terminal. See issue 8522. --

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Changes by Antoine Pitrou : -- assignee: -> brett.cannon components: +Tests nosy: +brett.cannon, haypo ___ Python tracker ___ ___ Pyth

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

New submission from Michael Foord : If you run test_warnings.py under an ascii terminal (at least on Mac OS X) then test_warnings.CEnvironmentVariableTests.test_nonascii fails. Perhaps the test should be skipped? == FAIL: tes