On 2018-03-23, Chris Angelico <ros...@gmail.com> wrote:
> On Fri, Mar 23, 2018 at 10:47 AM, Steven D'Aprano
><steve+comp.lang.pyt...@pearwood.info> wrote:
>> On Fri, 23 Mar 2018 07:09:50 +1100, Chris Angelico wrote:
>>
>>>> I was reading though, that JSON files must be encoded with UTF-8. So
>>>> should I be doing string.decode('latin-1').encode('utf-8')? Or does
>>>> the json module do that for me when I give it a unicode object?
>>>
>>> Reconfigure your MySQL database to use UTF-8. There is no reason to use
>>> Latin-1 in the database.
>>
>> You don't know that. You don't know what technical, compatibility, policy
>> or historical constraints are on the database.
>
> Okay. Give me a good reason for the database itself to be locked to
> Latin-1.
Because the DB administrator wont change things without orders from
his boss, who won't order changes without because there's no budget
for that.
OK, perhaps it's not a _good_ reason by your metrics, but reasons like
that are what you find in the real world.
--
Grant Edwards grant.b.edwards Yow! ... My pants just went
at on a wild rampage through a
gmail.com Long Island Bowling Alley!!
--
https://mail.python.org/mailman/listinfo/python-list
