[issue27424] Failures in test.test_logging

2016-08-05 Thread Emanuel Barry
Emanuel Barry added the comment: I'm not home to check, but judging by the error message and previous discussions with other developers, it seems indeed like an issue with a non-ASCII character in my hostname. I've changed my hostname since then, so I'm going to close this as won't fix. If it

[issue27424] Failures in test.test_logging

2016-08-03 Thread Vinay Sajip
Vinay Sajip added the comment: I am unable to reproduce this under Windows with either 32-bit or 64-bit Python, using revision 26dd6e7f. I used Windows 10 rather than 7 as that's all I can test on, but I don't believe it would make a difference. Is this error still reproducible? If not, I'll

[issue27424] Failures in test.test_logging

2016-07-01 Thread R. David Murray
R. David Murray added the comment: Domain names should never have non-ascii in them. They should be IDNA encoded. There is a known problem where Windows will return non-ascii domain names if the local hostname is configured naively (see issue 9377). SMTPUTF8 might be a workaround in

[issue27424] Failures in test.test_logging

2016-07-01 Thread INADA Naoki
INADA Naoki added the comment: Maybe, `socket.getfqdn()` returns non-ASCII string in your environment. smtpd.py has `-u` option which enables utf-8 support. smtpd.SMTPServer has enable_SMTPUTF8 option. test_logging.TestSMTPServer should enable this option. Could you test adding

[issue27424] Failures in test.test_logging

2016-06-30 Thread Emanuel Barry
New submission from Emanuel Barry: Ran the test as 'python -W error -m test.test_logging' on latest 3.6 version. No idea what causes this; full traceback attached. Not sure if it's relevant, but I'm running Windows 7. -- components: Library (Lib), Tests files: test_logging