progress, slowly. I need to refactor a lot of how I handle the debugging output for printing the image metadata table to avoid a lot of private accesses for things I don't wish to expose in the library as sensible things you should be able to read/write.

I also split out the command utility file into a bunch of sub-commands so it was easier to see where the lingering mess was; and surprise it's pretty much all in my "scan" command which is absolutely last on my list to fix until I fix everything else first.

I'd love to just shush pylint up here, but I know it's right about every last complaint it has here and I want to get to a smooth 0 error baseline before pushing to the public repo so it'll be easier to add individual changes/fixes/features in the future without worrying about if I've regressed something else ...

Really wish I was better at designing complex components, sheesh

but hey, mypy strict passing 100% is very satisfying ^_^

for some reason. its impossible to get anything relevant because all the answers i can find are for people who have Literally The Dumbest Problem and not my problem. anyway

hey so i'm adding pylint to an old project at work and its complaining about names like

C0103: Variable name "SomeCoolClass" doesn't conform to snake_case naming style (invalid-name)

obviously i can either rename the variable or add a comment disabling that error but i would like to conceptually fix it if possible... the thing is that this variable is not a variable but its a class definition returned by a method at runtime (inside another method), ex

def what():
    SomeCoolClass = give_me_the_class()
    a_thing = SomeCoolClass.create_a_thing()

now in this particular case i can put the give_me_the_class line at the top level and it doesn't complain but there's also places where that's not possible because it might not be registered at import time. anyway it's about a conceptual problem here: assume that the class getter can't be generated at import time, it's like dynamically generated by the method.

i also think it would be even worse to rename that class name to a snake case variable name because then it would look more like a class instance rather than a class definition to the passing eye and could easily cause mistakes.

is there really no solution except to disable that warning on that line? i've even tried things like adding type annotations to make it clear that its a class type, but i think pylint doesn't look at those?