Closed javierggt closed 7 months ago
Discussed in slack, but for the record:
OK now I understand.. the V1 code get_cmds
does actually call convert_bytestring_to_unicode
on the CommandTable
before returning it, but I got a bit too "clever" in the CommandTable
class. There is code in the class to basically force the column dtypes to be always consistent and uniform (which should be a good thing), but it goes too far and doesn't allow the bytes columns to be turned to unicode.
Unfortunately there was no unit test that confirmed the expected dtypes for v1.
We are not fixing this. When we transition to v2 this can be closed.
We have transitioned to v2.
Some dtypes in kadi commands changed in the latest version:
versus:
The one in 5.9.1 gives a table with bytes as opposed to unicode strings. That means that agasc supplement update will fail, because it used the
mp_starcat_time
strings as indices.