Repository navigation
Handle serializing dicts with ints and strings #3380
Description
Activity
@jonmmease is this something you could take a look at please? There's going to be some ambiguity if the same dict has
1and"1"as keys...Admittedly, that's an ambiguity that JSON imposes.
FWIW, this can be reproduced without plotly.py
import json json.dumps({'a': 0, 1: 0}, sort_keys=True)
TypeError: '<' not supported between instances of 'int' and 'str'The reason that we're hitting this now is that we switched to using
sort_keys=Trueduring theorjsonrefactor.As @chriddyp pointed out, there is a 2+ year long discussion in https://bugs.python.org/issue25457 on whether this is actually a bug in the Python 3 json module.
Maybe it was a mistake to set
sort_keys=True. This is the behavior of orjson, and at the time it seemed reasonable to align the output across json engines 🙂I don' t see a way to address this from within our custom
PlotlyJSONEncoder, so I see two options:- Remove
sort_keys=True, adjusting tests to accept that the json engines will not produce identical results - Try
json.dumpsand catch the exception. If the exception is raised, clone the input dict and modify it to convert non-string keys to strings before runningjson.dumpsagain.
Thoughts @nicolaskruchten ?
- Remove
Hmmm yeah, it kinda feels like "Remove sort_keys=True, adjusting tests to accept that the json engines will not produce identical results" is the safer route... basically getting folks to opt-in to
orjsonand any related constraints. Sorry!
The current
to_json_plotlydoesn't handle dicts with integers and strings as keys. This used to work before we setsort_keys=True.This is relatively common in Dash.
Here is a MWE:
Here is the issue in the Python tracker: https://bugs.python.org/issue25457 re
sort_keys=TrueOriginally reported in https://community.plotly.com/t/dash-2-0-0-migration-error/56478/7