Ruff improvements #392
Merged
Ruff improvements #392
Conversation
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
|
I love how ruff just works. LGTM |
MuellerSeb
approved these changes
Jul 24, 2025
|
Awesome! Yeah about the "it just works" bit... maybe we should have a beer together and think about code styles we like and which of these rules we want to include ;-) |
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.
Following up on PR #391, here are a few improvements, making it a little bit easier to work with ruff. Also, the CONTRIBUTIONS.md is now up-to-date. I don't think that we have to give a detailed list of our linter settings, as ruff automatically applies the settings we provide in the pyproject.toml file.
Keeping in the spirit of linting and standard formats, I have applied common formatting rules to pyproject.toml too.