Closed a13xp0p0v closed 2 months ago
I don't think that kernel-hardening-checker depends on ultra-modern python features, so supporting old-ish-but-still-maintained python version shouldn't add any overhead.
os.path
is going away soon. pathlib.Path
is the new "path"
os.path
isn't going anywhere soon, according to the documentation
from __future__ import annotations
is supported since Python 3.7.
It is used in ./kernel_hardening_checker/engine.py
.
Assignment expression or "walrus operator” NAME := expr
has been supported since Python 3.8.
It is used in ./kernel_hardening_checker/__init__.py
.
Closing this question for now. Supporting Python starting from v3.8 looks reasonable.
The CI scripts of
kernel-hardening-checker
run on Python versions that are currently officially supported: (from https://devguide.python.org/versions/)Question Should
kernel-hardening-checker
also work on some older Python versions? Is it needed on old machines? What do you think?