This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients ezio.melotti, serhiy.storchaka, sobolevn, vstinner
Date 2021-08-30.18:49:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630349394.49.0.57119073786.issue45053@roundup.psfhosted.org>
In-reply-to
Content
Test is failing because TESTFN contains now non-ASCII characters.

The path is written to stdout using the default stdout encoding on Windows (like cp1252), but test searches the path encoded with UTF-8. This test should fail also on other platforms with non-UTF-8 locale.

The simplest way to "fix" the test is using TESTFN_ASCII instead of TESTFN.

But there is also an issue in the script itself. It fails or produces a mojibake when the filesystem encoding and the stdout encoding do not match. There are similar issues in other scripts which output file names.
History
Date User Action Args
2021-08-30 18:49:54serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, ezio.melotti, sobolevn
2021-08-30 18:49:54serhiy.storchakasetmessageid: <1630349394.49.0.57119073786.issue45053@roundup.psfhosted.org>
2021-08-30 18:49:54serhiy.storchakalinkissue45053 messages
2021-08-30 18:49:54serhiy.storchakacreate