Nick Coghlan <ncogh...@gmail.com> added the comment: I can reproduce this, but it looks to me like it's being triggered by UTF-8 mode rather than locale coercion (the "LC_ALL=C" setting will implicitly disable locale coercion entirely):
``` $ LANG=C PYTHONCOERCECLOCALE=warn ./python -We -m test -uall -m test_strings test_gdb Python detected LC_CTYPE=C: LC_CTYPE coerced to C.UTF-8 (set another locale or PYTHONCOERCECLOCALE=0 to disable this locale coercion behavior). Run tests sequentially 0:00:00 load avg: 0.34 [1/1] test_gdb 1 test OK. Total duration: 2 sec Tests result: SUCCESS $ LC_ALL=C PYTHONUTF8=0 ./python -We -m test -uall -m test_strings test_gdb Run tests sequentially 0:00:00 load avg: 0.17 [1/1] test_gdb 1 test OK. Total duration: 2 sec Tests result: SUCCESS ``` I expect the fix will be to adjust test_gdb's expectations in this case, as there's going to be a genuine difference between gdb's locale dependent behaviour and Python's UTF-8 mode behaviour. ---------- nosy: +vstinner _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32834> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
