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
The Android stdout and stderr tests include an assertion that both streams are set to errors="backslashreplace", which is the most useful setting for redirecting the streams to the Android log. However, this test only passed because the CPython test harness reconfigures stdout – outside of the tests, it's set to surrogateescape.
…ythonGH-125943)
Android stdout/err streams now use `backslashreplace` encoding to ensure readability of the Android log.
(cherry picked from commit b08570c)
Co-authored-by: Malcolm Smith <smith@chaquo.com>
…H-125943) (#125950)
gh-125942: Android: set stdout to `errors="backslashreplace"` (GH-125943)
Android stdout/err streams now use `backslashreplace` encoding to ensure readability of the Android log.
(cherry picked from commit b08570c)
Co-authored-by: Malcolm Smith <smith@chaquo.com>
ebonnal
pushed a commit
to ebonnal/cpython
that referenced
this issue
Jan 12, 2025
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug description:
The Android stdout and stderr tests include an assertion that both streams are set to
errors="backslashreplace"
, which is the most useful setting for redirecting the streams to the Android log. However, this test only passed because the CPython test harness reconfigures stdout – outside of the tests, it's set tosurrogateescape
.CPython versions tested on:
3.13
Operating systems tested on:
No response
Linked PRs
errors="backslashreplace"
#125943errors="backslashreplace"
(GH-125943) #125950The text was updated successfully, but these errors were encountered: