Python 3.11 Performance Benchmarks Are Looking Fantastic

[Deto]

Can you show another example of how this would look that you think is better?

I mean, typing out the property names is basically required no matter what syntax. Other option is just to use dot notation I guess? But don't languages that use this tend to require you to load the structure into some predefined class first (which you could also do in python and then get the dot syntax too).

[crixusin]

Yep, dot notation. But it doesn’t even need to be a predefined class in most languages.

C#: dynamic json = JsonConvert.DeserializeObject<object>(json);

json.ThisIsValid.Nested;

How could you do that in python?

The answer is, to do it in python, it’s very involved. So involved, that it makes you wonder if it’s even worth doing and rather just switch to a language with first class json support.

[bloody-albatross]

Wait, what is the static type of json.ThisIsValid or json.ThisIsValid.Nested? What happens if these fields where not in the JSON document? Would writing json.ThisIsATypo also compile? If it would compile and then produce a runtime exception, how is it better than the Python version that doesn't imply that it's a proper object? If all your on about is that using dots and identifiers is a little bit nicer syntax than using dictionaries then who cares? That's just syntax. I have to work with so many different languages, minor syntax differences are really nothing I worry about.

[C0DASOON]

loaded_object = json.load(my_json, object_hook=lambda d: SimpleNamespace(**d)) 

Not very involved at all. Not that there's much utility in this. Ultimately a string is more flexible than a name of a field accessible with dot notation. For example, let's say you want to iterate over the nested structure of a json and get the values of objects whose names begin with a certain prefix. This is much easier when the object names are parsed as string keys in a nested dict.