We use Python-based EXEs to execute small, manageable jobs within C++ application. However, facing challenges in maintaining Python projects effectively: There is no version tracking for Python modules when generating EXEs. Developers use different Python versions and python module versions, leading to inconsistencies. We use Visual Studio for development. How can we standardize the development environment for Python projects within Visual Studio? Should all Python projects be under a single solution, and can we use a single requirements.txt file for all projects instead of separate ones? Currently, we generate EXEs using PyInstaller with the --onefile option, but this results in large EXE sizes. Can we use the --onedir option instead? If we do, can the dist/ folder be shared among all EXEs, so it can be included in the C++ application installation folder? What are the best practices for managing multiple Python EXEs efficiently in a C++-based application using Visual Studio? Continue reading...