A weird, error, something is wrong when using charset=binary to convert from whatever result mysql gives back into python:

~/venv/lib/python3.5/site-packages/mysql/connector/conversion.py in _DECIMAL_to_python(self, value, desc)
    446         Returns value as a decimal.Decimal.
    447         """
--> 448         val = value.decode(self.charset)
    449         return Decimal(val)
    450 

LookupError: unknown encoding: binary

@Neil_P._Quinn_WMF wmfdata sets this when doing mysql.connect.
https://github.com/neilpquinn/wmfdata/blob/master/wmfdata/mariadb.py#L63-L70

I see the same error that Irene does. Is binary what should be set here?

In T242448#5793730, @Ottomata wrote:

A weird, error, something is wrong when using charset=binary to convert from whatever result mysql gives back into python:

~/venv/lib/python3.5/site-packages/mysql/connector/conversion.py in _DECIMAL_to_python(self, value, desc)
    446         Returns value as a decimal.Decimal.
    447         """
--> 448         val = value.decode(self.charset)
    449         return Decimal(val)
    450 

LookupError: unknown encoding: binary

@Neil_P._Quinn_WMF wmfdata sets this when doing mysql.connect.
https://github.com/neilpquinn/wmfdata/blob/master/wmfdata/mariadb.py#L63-L70

I see the same error that Irene does. Is binary what should be set here?

Well, it's been that way for a long time, and has been working fine up until now. But I just figured out what caused it to break: it was working for me until I upgraded mysql-connector-python from 8.0.17 to 8.0.18 just now. Now, it throws the same error for me. Very odd since that should be just a patch release. I'll have to look into this more.

In T242448#5801373, @Neil_P._Quinn_WMF wrote:

However, the version of wmfdata with the fix is currently not working on due to a separate issue (T242683) so you won't be to try out this fix until that is resolved.

@Iflorez, that issue has been resolved too, so the latest version of wmfdata should work properly!