[issue26226] Various test suite failures on Windows when computer name contains a non-ascii character

Changes by ppperry : -- title: Various test suite failures on Windows -> Various test suite failures on Windows when computer name contains a non-ascii character ___ Python tracker

[issue26226] Various test suite failures on Windows

Emanuel Barry added the comment: That is good to know, thanks Eryk for the explanation! I also think making Python set LC_CTYPE on startup on Windows would be good. Martin's comment got me wondering, so I'm going to try to see if all modules properly got re-compiled, and re-run tests. I'll

[issue26226] Various test suite failures on Windows

Eryk Sun added the comment: time.strftime calls the CRT's strftime function, which the Windows universal CRT implements by calling wcsftime and encoding the result. The timezone name is actually stored as a char string (tzname), so wcsftime has to decode it via mbstowcs. The problem is that

[issue26226] Various test suite failures on Windows

Martin Panter added the comment: test_distutils: Is the failure the same as before, or changed? Are you testing with new code that includes the Issue 27048 fix? It looks like test_distutils doesn’t support running directly via “unittest”. Perhaps try “python -m test -W test_distutils” or

[issue26226] Various test suite failures on Windows

Emanuel Barry added the comment: About the strptime failure - it seems time.strftime returns "Est (heure d?été)" while _strptime.LocaleTime().timezone has "est (heure d\x92été)". I don't know why it's like that, but neither are correct - the character that goes there is a single quote (').

[issue26226] Various test suite failures on Windows

Emanuel Barry added the comment: Some of the tests that used to fail are now passing, however some are still failing (and new ones are also failing now). Tests that are still failing: test_code_module (TestInteractiveConsole; test_ps1 and test_ps2 failed) test_codecencodings_iso2022 (blame

[issue26226] Various test suite failures on Windows

R. David Murray added the comment: It looks like this issue can be closed, but a new one should be opened for dealing with the newline issue under git on windows. However, I'm surprised there weren't failures in the email tests. Although I've been moving the email tests away from depending

[issue26226] Various test suite failures on Windows

STINNER Victor added the comment: It looks like all issues are now fixed in the default branch, no? Can we close this issue? -- ___ Python tracker ___

[issue26226] Various test suite failures on Windows

Martin Panter added the comment: Regarding the files getting messed up in Lib/test/cjkencodings, IMO the solution is to not configure Git to mess with newlines in files. ;) But perhaps a reasonable workaround might be to rename the relevant files to something like *.txt.bin. Perhaps that will

[issue26226] Various test suite failures on Windows

Ezio Melotti added the comment: > I'm surprised by the test_codecencodings_iso2022 failures. Example: == FAIL: test_incrementaldecoder (test.test_codecencodings_iso2022.Test_ISO2022_KR)

[issue26226] Various test suite failures on Windows

Changes by Ezio Melotti : -- nosy: +ezio.melotti type: -> behavior ___ Python tracker ___

[issue26226] Various test suite failures on Windows

STINNER Victor added the comment: For the test_httpservers failure, can you please try the following commands on your PC? >>> socket.gethostname() 'selma' >>> socket.gethostbyaddr(socket.gethostname()) ('selma', [], ['2a01:e34:ec8d:4c70:3ea9:f4ff:fe65:c0c', 'fe80::3ea9:f4ff:fe65:c0c'])

[issue26226] Various test suite failures on Windows

STINNER Victor added the comment: I'm surprised by the test_codecencodings_iso2022 failures. Example: == FAIL: test_incrementaldecoder (test.test_codecencodings_iso2022.Test_ISO2022_KR)

[issue26226] Various test suite failures on Windows

Changes by Emanuel Barry : -- stage: -> needs patch versions: +Python 3.6 ___ Python tracker ___

[issue26226] Various test suite failures on Windows

New submission from Emanuel Barry: Compiled latest master and ran test suite (Py_DEBUG build). A few failures here and there, and some tests skipped. I haven't yet looked into getting the proper libraries to make some of the skipped tests execute, I'm trying to make the whole test suite pass

[issue26226] Various test suite failures on Windows

STINNER Victor added the comment: Python 2.7.11: >>> import socket >>> socket.gethostname() '\xc9manuel-PC' This one works on Python 3 because the Python function is implemented with a call to the Windows native API. >>> socket.gethostbyaddr(socket.gethostname()) ('\xc9manuel-PC.home', [],

[issue26226] Various test suite failures on Windows

Emanuel Barry added the comment: Well, it has a non-ASCII character in it, so I wouldn't be surprised if this was the issue :) Latest master (3.6): >>> import socket >>> socket.gethostname() 'Émanuel-PC' >>> socket.gethostbyaddr(socket.gethostname()) Traceback (most recent call last): File