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 ncoghlan
Recipients ncoghlan, serhiy.storchaka, vstinner
Date 2018-02-13.02:33:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1518489213.13.0.467229070634.issue32834@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2018-02-13 02:33:33ncoghlansetrecipients: + ncoghlan, vstinner, serhiy.storchaka
2018-02-13 02:33:33ncoghlansetmessageid: <1518489213.13.0.467229070634.issue32834@psf.upfronthosting.co.za>
2018-02-13 02:33:33ncoghlanlinkissue32834 messages
2018-02-13 02:33:32ncoghlancreate