submitted 1 year ago by sisyphean@programming.dev to c/python@programming.dev

8 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] Andy@programming.dev 1 points 1 year ago

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.

[-] jnovinger@programming.dev 0 points 1 year ago

You should make a post about NestedText. That looks interesting and pretty close to my own internal note-taking style.

[-] Andy@programming.dev 0 points 1 year ago

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.

[-] jnovinger@programming.dev 1 points 1 year ago

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 file
validating NestedText content with Pydantic, particularly something like the example Django settings they provide

Thinking about how I might use it:

Meeting notes
A personal log of todo items, observations, feelings during the day
Scoring a baseball game using a more sane version of Retrosheet's Event File format
A possible human AND machine readable format for Architectural Decision Records