All right, here's where things are on the task runner:
- I decided that my hangups around the latest Pijul release acting weird were basically procrastination, so I've started the project regardless, but for now it's in a more traditional VCS with a more established user base and maintenance. I am referring, of course, to Mercurial.
- Because I've got all or nearly all of the core logic sketched out in the prototype, I figured I'd experiment a bit with Cement, since my complaint from the last time I looked into it ("They're telling me how to start a project, but I already have a project!") doesn't apply.
- I started the quickstart, and just filled in my info for the values instead of the todo-list stuff, and committed the results.
It's... probably fine. There's just a few things I would change...
- It's using setup.py and all that entails, including MANIFEST.in. I'd rather use Flit.
- The runtime requirements don't appear to be specified in the setup.py file, so I don't think this can be packaged and expected to work.
- I don't know what version scheme "0.0.1" is, but it's neither SemVer nor CalVer.
- No src directory.
- Why do all of these files start with a newline? I don't have any coherent objection to this, because I just don't understand.
And, in stuff that's less certain/defensible...
- I had a lot better time using towncrier with Pip than I ever did editing CHANGELOG files.
- I'd generally rather use reStructuredText than Markdown. Not because of anything about the syntax, but because I understand Sphinx just well enough by now.
- Speaking of which, there's a docs directory, but I don't think anything interacts with it? What's up with that?
- Until my task runner is off the ground, I'm going to replace the Makefile with a noxfile, and probably redo the layout of the repository so I can have a separate package for basic extensions.
So, you know, there are a few tiny changes I'm going to make before I get back to following along with the tutorial. I'll see about getting on those tomorrow.