Three Dollar Quill

Okay. Okay. I've got some interesting results from throwing stuff into SymPy, and carefully tweaking the output, but I won't know if I got things at all right unless I turn this into working code. And that's a little problematic, because the expressions I'm working with are dense blocks of over five thousand characters each (with significant amounts of whitespace omitted), and the current monolithic module powering all of this is already a little long for my comfort, at several hundred lines. The code isn't precisely where I want it to be in terms of the interfaces between classes, but it's not much of a leap to get it there.

Except.

That there are no tests, and I'm working with this all manually. I need to write tests if I want any confidence in a big rewrite, and I need to figure out where tests go to write them. This wouldn't be tricky in a full-on package layout, but I'm changing pace and loosening up a bit for this work; I've actually got a bunch of unrelated projects comingling in the same environment, with just uv to provide some semblance of order. Since there's no broader directory for each project than the package directory, and I kind of don't feel like putting in the work for it, I think that means the tests have to go in the packages themselves. Here's what I need to refresh my memory on to get such a layout working:

• pytest guidance on in-package tests
• resource file discovery

...

Okay, I did that, and a few other things, and now I've got an easy-to-use test runner that's verified to work in this configuration I just threw together. I've laid the groundwork for pulling this stuff apart, and I'll be duplicating it across the other packages that are coexisting with this code, but right now I want to wind down.

Good night.