Comment 3 for bug 2020064
Revision history for this message
| Michael Atkins (neroprotagonist) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I had the same error on one client machine and not another one even though both machines had LANG=en_GB.UTF-8 in /etc/default/locale and ran identical python version 3.8.10.
After some debugging using strace I found that the solution was to install/configure the en_US.UTF-8 locale using
dpkg-reconfigure locales
and making sure the en_US.UTF-8 was selected.
Also, I don't think a fix should alter the locale on a client machine (i.e. using update-locale) given that the whole point in locales is to support different regions and you would prevent the client from achieving this.