Previously we were using py -3 to run python on Windows machines, however after we activated the python venv, the python executable is just python. We had a few machines that had some corrupt or broken global python installs (#4242) and so jobs were failing on them, with this change we will now be properly isolated from issues with the global python installation.
In addition, I also added an extra command after venv activation to re-enable echo. For some reason the venv activation script turns echo off and then doesn't re-enable it at the end, so with this change we can now see all the commands that are run inside the venv on Windows.
Previously we were using
py -3to run python on Windows machines, however after we activated the python venv, the python executable is justpython. We had a few machines that had some corrupt or broken global python installs (#4242) and so jobs were failing on them, with this change we will now be properly isolated from issues with the global python installation.In addition, I also added an extra command after venv activation to re-enable
echo. For some reason the venv activation script turnsechooff and then doesn't re-enable it at the end, so with this change we can now see all the commands that are run inside the venv on Windows.