No no, is out of the standard. The parsers should strict follow the standard.

obs: Is just what I'm hearing these days. I'm just curious to hear what Mr PowerShell would argue.

No no, PowerShell is bad and should never exists as this accepts invalid JSON.

If PowerShell was strict about JSON I would be able to reuse the line in Python, what was not the case. But I was expecting something not so strict, as people say that Python is easy. My bad...

And I'm "attacking" the fan base not the community. And I really agree with @pmaris.bsky.social that using something that is not so strict is dangerous. This all thing begin because I'm migrating from PowerShell to Xonsh and I face this issue with my one line 'JSON' config for internal build.

Are you afraid that I will delete the posts? This is my real first and unique life profile, I show my face and I take responsibility for my opinions. My JSON, or whatever it is, is not invalid and I can use it with PowerShell without any problem.

If you are looking for a permissive json library for python, you can try json5.
>>> import json5
>>> json5.loads("{ arch: 'arm64', torizon_arch: 'aarch64' }")
{'arch': 'arm64', 'torizon_arch': 'aarch64'}

but remember you are not doing json!

Are you right. I'm wrong, sorry to disrespect your facts.

I do not hate Python. I like to pay my bills.

Is only a matter of strictness. My point, as all from Python ecosystem is new for me, is that Python is not as easy or friendly as people rush it. It sometimes is so stricness that I think I should use C/C++ instead. I'm more productive using C#, PowerShell or JS when I need something "easy".

🤔

And as I'm saying, is not valid for Python 🤦

The other thing that annoys me is how Python fans don't accept that Python and its ecosystem is not perfect and is in fact complicated.

not for all, but for Python yes. The only thing that annoy me is that they say that Python "is straightforward and bla bla bla", but there are silly things that it insists on being so strict ...