Fix ruff

[MaximSmolskiy]

Describe your change:

Fix ruff

• Add an algorithm?
• Fix a bug or typo in an existing algorithm?
• Add or change doctests? -- Note: Please avoid changing both code and tests in a single pull request.
• Documentation change?

Checklist:

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized.
• I know that pull requests will not be merged if they fail the automated tests.
• This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
• All new Python files are placed inside an existing directory.
• All filenames are in all lowercase characters with no spaces or dashes.
• All functions and variable names follow Python naming conventions.
• All function parameters and return values are annotated with Python type hints.
• All functions have doctests that pass the automated testing.
• All new algorithms include at least one URL that points to Wikipedia or another similar explanation.
• If this pull request resolves one or more open issues then the description above includes the issue number(s) with a closing keyword: "Fixes #ISSUE-NUMBER".

[MaximSmolskiy]

@cclauss please review and tell me is it a normal situation that last commit to master has green status, but at the same time on new commits to master ruff crashes?

[cclauss]

Ruff is v0.9.1 almost at v1.0 where it will be more stable but for now we can expect some bumps like this. V0.9.0 also added the 2025 stable format which is shared between black and ruff format. We could run ruff only in pre-commit but I like running unpinned in GitHub Actions so we spot the changes.

[cclauss]

Nice!