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 vstinner
Recipients koobs, ncoghlan, vstinner
Date 2018-11-22.14:01:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I'm wondering if we may need to make test_c_locale_coercion less opinionated, where for most platforms it's just a "don't segfault" test, and it's only for ones where we're certain about how we expect it to behave (i.e. Linux, Mac OS X, AIX, maybe FreeBSD) that we try to check the specifics.

For test_embed, I tried to be smart to guess the encodings (ex: hardcode some encodings depending on  the platform) and... I gave up. It's very hard when you consider Linux, Windows, macOS, FreeBSD, but also HP-UX and AIX. Each platform has weird cases about encodings... Now the test spawns a Python subprocess to get the encoding. See get_stdio_encoding() and get_filesystem_encoding() in Lib/test/
Date User Action Args
2018-11-22 14:01:57vstinnersetrecipients: + vstinner, ncoghlan, koobs
2018-11-22 14:01:57vstinnersetmessageid: <>
2018-11-22 14:01:57vstinnerlinkissue35290 messages
2018-11-22 14:01:57vstinnercreate