You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix the "backslashreplace" tests for the functional API to be
endian-agnostic. The tests used to rely on `.encode("utf-16")`
producing the same data as found in the test file. However, on big
endian platforms it would produce a big endian encoding, while the test
file is little endian. To avoid the problem, explicitly specify
`utf-16-le` encoding. Since this meant that the BOM is no longer
produced, explicitly include it in input.
Fixespython#312
Thanks for the report. It looks like this issue was also reported downstream at python/cpython#117569. Since there's already a fix there, I'm going to apply that one here to keep things in sync.
When running the tests on big-endian architectures (sparc64, ppc64), we're getting the followin test failures:
Reproduced with be5a270. I'll submit a PR shortly.
The text was updated successfully, but these errors were encountered: