Add pre-commit, ruff check configuration and Github action#405
Merged
hugovk merged 20 commits intopython:mainfrom Sep 3, 2025
Merged
Add pre-commit, ruff check configuration and Github action#405hugovk merged 20 commits intopython:mainfrom
ruff check configuration and Github action#405hugovk merged 20 commits intopython:mainfrom
Conversation
AA-Turner
reviewed
Sep 1, 2025
AA-Turner
reviewed
Sep 1, 2025
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
AA-Turner
reviewed
Sep 1, 2025
hugovk
reviewed
Sep 2, 2025
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Contributor
Author
|
@hugovk Voilà! Thank you for a beautiful review. Some notes:
|
hugovk
reviewed
Sep 2, 2025
Member
It's very important we can compare new benchmark runs with old ones, so let's just leave them be. We want to benchmark some sort of "real-life code", and unused variables is often part of that :)
Yes, makes sense. We can do it in followups. We might want to autoformat the code and keep ignoring E501.
Yeah, again it's safer to just leave the actual benchmarks as-is, but we could do a sweep of the benchmark-running code. I've used vulture a bit, there's also deadcode which is similar, but deadcode has nice colour output. |
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
This was referenced Sep 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After #404, I ran
uvx ruff checkand found a lot of not so subtle errors:Including benchmarks:
It makes one wonder how much of this code is actually dead...