I don't have much to say besides, good job. We all believe in you.

Looking at the thinkTank website, I think you're talking about the Secure Pocket Rocket model, but I'm not sure.

Includes pytest integration: https://github.com/adamchainz/time-machine#pytest-plugin

I've only used pyenv on Ubuntu machines, but I expect it would work just as well in Debian-based systems.

pyenv is really useful if you need multiple versions installed simultaneously and it handles installation for you.

https://github.com/pyenv/pyenv

My post's link is to the original blog URL that you point to, I just mentioned the author's Mastodon post where I ~~ran~~ first saw a reference to the blog post.

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

I've mostly resisted the urge to use a dotfile manager so far, but I'm starting to feel like it's time. I was excited when I ran across this one and noticed it was written in Python and had Git-like semantics.

Will play with it this weekend and report back.

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

This is great! I really appreciate that it returns a sensible exit code to the shell so that it can potentially fail a build. I also like the ability to maintain a list of excluded names in pyrpoject.toml so that you don't always have to sort through false positives.

Would love to see some more output options, like maybe --quiet that simply passes/fails and returns the exit code with no output or --count that either just displays a count or includes a count in the regular output. I guess I could always pipe the output to wc -l instead of having --count.

I'll see if I can't get this integrated in our CI system at work this next week.

Next experiment is Talk Tuesday where each top-level comment is about a particular conference talk that a commenter liked and why they like it.

My favorite PyCon talk comes from, who else, Raymond Hettinger at PyCon US 2013 and is titled Transforming Code into Beautiful, Idiomatic Python.

I had been a Python developer for maybe a year-and-half at this point and was starting to grok some more advanced concepts. But, I remember walking out of that talk thinking about how excited Raymond was about Python and how to make Python code beautiful. I'm sure I've forgotten a few, but most everything I learned about in that talk (like context managers, looping over dictionary key/value pairs, counting with dictionaries, and decorators) have all really stuck with me and influenced how I tackle problems.

I'm personally still loving Regolith Desktop on top of Ubuntu/Debian.