misc: ruff rules E741 and YTT204

[cclauss]

% ruff rule YTT204 sys-version-info-minor-cmp-int

% ruff rule E741

ambiguous-variable-name (E741)

Derived from the pycodestyle linter.

What it does

Checks for the use of the characters 'l', 'O', or 'I' as variable names.

Note: This rule is automatically disabled for all stub files
(files with .pyi extensions). The rule has little relevance for authors
of stubs: a well-written stub should aim to faithfully represent the
interface of the equivalent .py file as it exists at runtime, including any
ambiguously named variables in the runtime module.

Why is this bad?

In some fonts, these characters are indistinguishable from the
numerals one and zero. When tempted to use 'l', use 'L' instead.

Example

l = 0
O = 123
I = 42

Use instead:

L = 0
o = 123
i = 42

[cclauss]

Someone who knows Numpy should look at the issues at: ruff check select=NPY.

Also, ruff check select=E722

Why is this bad?

A bare except catches BaseException which includes
KeyboardInterrupt, SystemExit, Exception, and others. Catching
BaseException can make it hard to interrupt the program (e.g., with
Ctrl-C) and can disguise other problems.

[boomanaiden154]

LGTM.

From https://docs.astral.sh/ruff/rules/sys-version-info-minor-cmp-int/ outlining the motivation for YTT204 since I didn't see a large benefit at first:

Comparisons based on the current minor version number alone can cause subtle bugs and would likely lead to unintended effects if the Python major version number were ever incremented (e.g., to Python 4).

[Malekkimo]

---