Skip to content

Improve python tooling #1088

Description

@dangotbanned

Description

In a similar vein to (#1087) I've run into a few other issues.
The general theme for fixes are:

  • Configuration that makes existing tooling more useful
  • Ensuring the (python) test suites are green1 by default

The end result? More things that just work™ and we get helpful feedback for things that don't/may not

Issues

I may split some of these out into other issues if they start looking big or a theme emerges.
Most can be individual PRs, just wanting to see them organized for now:

Pytest

Ruff

Not sure if this was intentional, but I will mention it here:
most of what ruff can do is disabled.

Is that so bad?

I'd consider that a risky combination with LLM usage, or at least more expensive to fix than having Ruff do it 😄

I'm not looking to resolve the above here, but these should be quick, uncontroversial wins:

Important

Ruff's new default rule set will fix most of this - but will be alarming in CI

Typing

Misc

Footnotes

  1. Or at least yellow with expectations

Metadata

Metadata

Assignees

No one assigned

    Labels

    pythonPull requests that update Python code

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions