The current code is locked into Python 3.8 (the version of Python that the OpenStudio/EnergyPlus versions we are using use). This version of Python is now somewhat past its EOL now, so we should do something about that. On my development VMs, I'm relying on the fact that the system Python is version 3.8, so I can safely point EnergyPlus at the site-packages directory and we can use everything installed there. There are many tools out there (including hatch) that provide good Python version management, so we should not be relying on the system Python going forward.
The current code is locked into Python 3.8 (the version of Python that the OpenStudio/EnergyPlus versions we are using use). This version of Python is now somewhat past its EOL now, so we should do something about that. On my development VMs, I'm relying on the fact that the system Python is version 3.8, so I can safely point EnergyPlus at the
site-packagesdirectory and we can use everything installed there. There are many tools out there (including hatch) that provide good Python version management, so we should not be relying on the system Python going forward.