The translate-modules script was having problems because it used the waftlib package, which is available in the virtual environment. So in order to use the virtual environment, the python script needed to be moved invoked by a bash script so that it can use .venv/bin/python. But the use of the bash script removed the need for the waftlib import alltogether, so .venv/bin/python is not necessarily needed over the system's python binary. However, it is still useful to use the virtual environment, because the translate-modules script depends on package deepl when using the --use-translation-service option, and deepl can be made available in the virtual environment.
… file that is invoked by a bash script.
The translate-modules script was having problems because it used the waftlib package, which is available in the virtual environment. So in order to use the virtual environment, the python script needed to be moved invoked by a bash script so that it can use
.venv/bin/python. But the use of the bash script removed the need for the waftlib import alltogether, so.venv/bin/pythonis not necessarily needed over the system's python binary. However, it is still useful to use the virtual environment, because the translate-modules script depends on packagedeeplwhen using the--use-translation-serviceoption, and deepl can be made available in the virtual environment.