Explicitly use python3 and pip3 executables

[timmoon10]

Description

Not all systems configure python to point to the Python 3 executable. For example, try installing Python in an Ubuntu Docker container and calling python:

docker run ubuntu:24.04 bash -c "apt-get update && apt-get install -y python3 && python --version"

This will fail with:

bash: line 1: python: command not found

This PR explicitly specifies python3 and pip3 so it can work on such systems. This will be especially helpful for testing.

I've also replaced some Python executables (Pylint, cpplint, pre-commit) with python -m. I don't like running containers as root, so Pip installs locally and the executables are not in my PATH.

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

• Explicitly use python3 and pip3 instead of python and pip
• Run Pylint, cpplint, and pre-commit with python -m

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[timmoon10]

/te-ci

[timmoon10]

/te-ci core pytorch jax L0 L1