chore: satisfy linting concerns from ruff

[2bndy5]

• a step toward resolving adopt pre-commit #138

[2bndy5]

About check=True concern.

[tekktrik]

Some minor changes but all of these look good. We could push the line length out but I think this is still fine and readable for now.

[2bndy5]

I think the typing concerns would be better addressed using mypy. But the pre-commit config (proposed in #144) does not currently include mypy usage. Would you like another PR to add mypy into the CI (and fix any any typing problems that arise)?

[tekktrik]

I would separate mypy. I think type annotation here are helpful for the developers, but this isn't intended to be a widely used library - so the work needed for compliance per mypy may not be worth it in that regard. That's likely more true if mypy adherence would require any sort of major overhaul.

[2bndy5]

so the work needed for compliance per mypy may not be worth it in that regard

FYI, I spent almost 20 minutes trying to track down the types of the parameters you questioned. Using mypy can avoid wasting that much time.

A quick run of mypy shows that most problems originate from not having type stubs for dependencies. If that result remains persistent, then it would be beneficial for maintainers alone.

[tekktrik]

Thanks!

[2bndy5]

It turns out that the typing here is much more of a mess than I thought. Honestly addressing the typing errors/warnings would feel like a total rewrite, and, at that point, I would just use rust with a python binding.