The s_python script does not limit itself to inspecting files tracked by git, and can end up looking in build directories. For example:

####################### MESSAGE ############################
s_all run of: "./s_python" resulted in:
    [tab] characters appear in Python scripts:
    	./build/bench/wtperf/venv/lib/python3.10/site-packages/psutil/tests/test_linux.py
    	./build/bench/wtperf/venv/lib/python3.10/site-packages/wheel/macosx_libfile.py

Rather than simply finding each Python file, we should either use git, or an allowlist approach like comment_style.py. Note that if using git, there needs to be a fallback - we can't always assume the command is being run from within a git repository (e.g. for the standalone release tarball).