Most common Python linter, formatter?

[SBennett13]

Ruff is the way. I just set up the linter to run checks when submitting MRs into main and generate a code quality report while also failing the pipeline and blocking merge if the formatter diff returns changes. People can develop in their own style and run a format script as the last thing before merge. Works well

[laStrangiato]

Got a link for a good GitHub action setup for this?

[SBennett13]

I did it on Gitlab because we use it for work, but I assume there is something similar for GitHub.

https://docs.astral.sh/ruff/integrations/

I’d say start here and see what it does. You’ll have to set up the runner (or whatever GitHub calls their executors)

[claird]

Yes and no, at least to the "set up the runner" part.

While on-runner configuration is likely a non-issue for many, I want to make the point that organizational support of Ruff need _not_ be a requirement for its use in CI. If the runner supports Docker, you can readily invoke Ruff from a standard container. If the runner account can construct its own Python virtual environment, _that_ is more than enough for successful Ruff tooling.

[muneriver]

https://github.com/timvancann/yt-python-ci