Deploy: pip_requirements step invokes prepare_env script that erases current .env and recreates it from scratch.
But some old (very old) systems still have python3.6 as default python3.
Thus prepare_env creates virtual env with python3.6 and fails to install packages that are not 3.6 compatible.
Is it possible to keep current .env and just install pip requirements or allow to specify python3 version for new virtual env?
Deploy:
pip_requirementsstep invokesprepare_envscript that erases current.envand recreates it from scratch.But some old (very old) systems still have
python3.6as defaultpython3.Thus
prepare_envcreates virtual env withpython3.6and fails to install packages that are not3.6compatible.Is it possible to keep current
.envand just install pip requirements or allow to specifypython3version for new virtual env?