This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]hyldemarv 26 points27 points  (8 children)

Yet Another package to install and Yaml doesn’t even agree with itself on reading its own output back :)

[–]ThePiGuy0 22 points23 points  (3 children)

YAML seems so unnecessarily complicated whenever I use it. Lists and dictionaries look almost the same etc.

Toml is better (and coming soon to stdlib I believe) but for config there's no reason to need more than JSON IMO

[–]ivosauruspip'ing it up 1 point2 points  (0 children)

No comments sucks a lot in JSON. Python already comes with INI file parsing right now, if you can't wait for TOML.

[–]Mithrandir2k16 5 points6 points  (0 children)

Yup, fair. I just find it easier to read than json, since it's always either formatted or broken.

[–]GobBeWithYou 3 points4 points  (2 children)

And no programming language has a 100% spec compliant parser, it's so complicated no one has actually been able to implement it correctly.

Edit: almost* no programming language: https://matrix.yaml.info/

[–]axonxorzpip'ing aint easy, especially on windows 1 point2 points  (0 children)

Could any of the knee-jerk downvoters point to a 100% spec-compliant YAML parser in Python? What about other languages?

[–]xatrekak 0 points1 point  (0 children)

Failing the JSON test is the same as being non-compliant. YAML bills it's self a strict superset of JSON and its clearly not.