Ned Deily added the comment:
Thanks for the report. There was a lengthy discussion of this behavior a few
years ago in Issue3067. At that time it was decided not to change this
behavior for 2.7. I'm not sure if the __future__ "unicode_literals" was
considered then, however you can work around it by using the b"" literal syntax:
locale.setlocale(locale.LC_ALL, b'POSIX')
----------
nosy: +ned.deily
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> setlocale error message is confusing
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20793>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
