New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch to Ruff for code quality #546

Open

ahobeost opened this issue Sep 30, 2024 · 1 comment

Assignees

Contributor

ahobeost commented Sep 30, 2024

As a developer, any speedup in common feedback cycles is welcome.
That is, as long as it does not come with a major downside.

When checking for linting and formatting, feedback can be very slow (e.g. 1 min for tiny changes).
Ruff could seriously reduce this time.

Downside:

Upside:

Ruff could completely replace black
Pylint could be used to only check for the vital things missing in Ruff.

ahobeost modified the milestone: bug fixes Sebastian

ahobeost assigned sebastian-swob

Contributor Author

ahobeost commented Oct 4, 2024

@sebastian-swob
Just compare the current pylintrc file with a new one.
https://stackoverflow.com/questions/22448731/how-do-i-create-a-pylintrc-file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment