Closed georgeharker closed 2 years ago
See here for a proposed fix that seems relatively clean. Not quite sure how to up the coverage numbers.
Thank you @georgeharker. I've checked your bugreport and your fix for it and it seems good to me. I will make a release for it.
Consider:
Without the strict settings this prints
Because of the use of strict, when
default_dict_deserializer
attempts to deserialize-keys
it fully decodes the key, and then attempts to be decoded again during the subsequent decode of the dict values / construction of the result. I have a hack that returns whether_load_hashed_keys
found stored keys, and skips the duplicate deserialize on the keys in that case, but it's probably a bit ugly, and I wonder whether there's a cleaner fix.