Make some automated optimizations using ruff

[cclauss]

Description

Make some automated optimizations via the command: ruff check --select=PD,RET,RSE,RUF,SIM --fix --unsafe-fixes

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

% ruff check --select=PD,RET,RSE,RUF,SIM --statistics

7	SIM401	[*] if-else-block-instead-of-dict-get
4	SIM210	[*] if-expr-with-true-false
3	SIM108	[*] if-else-block-instead-of-if-exp
2	PD002 	[*] pandas-use-of-inplace-argument
1	RSE102	[*] unnecessary-paren-on-raise-exception
1	RET506	[*] superfluous-else-raise
1	PD011 	[ ] pandas-use-of-dot-values
1	RUF010	[*] explicit-f-string-type-conversion
1	RUF100	[*] unused-noqa
[*] fixable with `ruff check --fix`

% ruff check --select=PD,RET,RSE,RUF,SIM --fix --unsafe-fixes

Found 23 errors (22 fixed, 1 remaining).

% ruff rule SIM401

if-else-block-instead-of-dict-get (SIM401)

Derived from the flake8-simplify linter.

Fix is sometimes available.

What it does

Checks for if statements that can be replaced with dict.get calls.

Why is this bad?

dict.get() calls can be used to replace if statements that assign a
value to a variable in both branches, falling back to a default value if
the key is not found. When possible, using dict.get is more concise and
more idiomatic.

Under preview mode, this rule will
also suggest replacing if-else expressions with dict.get calls.

Example

if "bar" in foo:
    value = foo["bar"]
else:
    value = 0

Use instead:

value = foo.get("bar", 0)

If preview mode is enabled:

value = foo["bar"] if "bar" in foo else 0

Use instead:

value = foo.get("bar", 0)

References

• Python documentation: Mapping Types

Related Issue

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[nvuillam]

@cclauss thanks for the PR :)

Please can you check the CI issues ? (don't bother about trivy ones, I should handle them in another PR)