Feature Request: Allow custom python path in config instead of relying on PATH

[ryq1212]

I already have Python and PyTorch installed on my system, and everything is set up properly. However, I deliberately did not add Python to the system PATH because I maintain multiple Python-based projects and want to avoid unnecessary conflicts.

At the same time, I would prefer not to use the embedded Python that comes with Flowframes, since it takes up additional space even though I already have fully functional environments.

Therefore, I’d like to suggest adding an option in the configuration to manually specify the path to python.exe, instead of relying solely on the Python version found in the system PATH. This would allow users like me to reuse an existing Python installation without installing the embedded one, while keeping multiple environments clean.

[eric15342335]

I am using a Python 3.13 virtual environment created with uv on Windows 11. Launching Flowframes with the following script works for me:

setlocal

rem Change to this script's folder so that relative paths work
cd /d "%~dp0"

rem Activate the Python venv for cmd.exe
call ".venv\Scripts\activate.bat"

rem Run Flowframes.exe without spawning a new window, then wait for it to exit
start "" /b /wait "%~dp0Flowframes.exe"