I think yaml was a perfectly fine way to express a hash/dict like config. I am surprised that toml was so widely adopted by the community.
YAML is extremely complex for a configuration format and it has many really weird edge cases:
The problem is IMHO made worse because it looks so friendly at first glance.
Yaml is fine until you want to abbreviate Norway and get false... toml doesn't handle everything well but at least it doesn't have insane problems like that.
While that shouldn't happen with a current-spec YAML parser, I agree even the current spec does way too much with types.
I've come to love NestedText's approach of leaving all type handling to the ingesting code.
You should make a post about NestedText. That looks interesting and pretty close to my own internal note-taking style.
Would you suggest a topic or tooling to pair with it, so I can provide a good demo for working with it in a real and useful context?
I made a CLI tool for working with it but want to avoid making a look-at-me spammy post, and I think the NestedText site itself explains the ideas pretty well already.
First, I have to apologize, I just meant post a link to NestText as a post in c/Python. I definitely didn't mean to imply you should have to go write a blog post (or something) about it just for me. I swear this was just an attempt to get another person posting interesting things to c/Python. 😬
Looking through the community projects and docs, the use cases/tooling that really stood out to me were:
parametrize_from_file, for defining pytest parametrize params in a fileThinking about how I might use it:
As someone who had tried to wrap their mind around YAML spec...
Fuck yaml. It is ridiculous how much junk there is in that spec.
I love toml. It's so natural. I use it all the time (for smaller configs)
Welcome to the Python community on the programming.dev Lemmy instance!
October 2023
November 2023
Past
July 2023
August 2023
September 2023