Improve Python interpreter detection and exclude virtual environments

[leobz]

The current build configuration has two issues:

1. Python interpreter detection: The Makefile relies on the python alias, which may not exist on some systems. To ensure compatibility, it should use python3 when available, while still supporting the python alias if present.

2. Virtual environment tracking: The venv/ directory appears in git status as untracked files, which should not be version controlled.

Solution

Update Makefile to automatically detect python3 with fallback to python.

Add venv/ to .gitignore to exclude virtual environment files.

Impact

Improves compatibility across different Python environments.

Prevents accidental commit of virtual environment files.

[eldipa]

Hi, I respond by item:

Python interpreter detection: The Makefile relies on the python alias, which may not exist on some systems. To ensure compatibility, it should use python3 when available, while still supporting the python alias if present.

You can specify to run python3 from command line like byexample -l python3.

If you are talking about the building/testing process (aka the Makefile), there is a env var that control which binary to use called python_bin. Depending of the user's environment, python may be linked to python3 as it is common when using pyenv and similar. Still, the user can change it if she wants.

Virtual environment tracking: The venv/ directory appears in git status as untracked files, which should not be version controlled.

Ok, but there is no action on my part. If the user is creating a venv folder in the same folder that cloned the git project, it is up to her to either adding it to hers gitignore, create the venv folder in other place or just ignore the issue.

I don't see the point to add a specific rule to ignore venv in gitignore. What if the user calls the folder differently like env3?
Do you have in mind an angle that I may be missing?