remove python 3.10 pin in run_win_build.bat template

[h-vetinari]

For https://github.com/conda-forge/google-cloud-cpp-feedstock, I need to use an older lief due to conda-forge/lief-feedstock#45 causing the build to time out otherwise. This started failing recently, as our default python version in the image seems to have moved to 3.12, for which we have no lief<0.14 builds.

Once I add a python=3.11 pin to remote_ci_setup, things work out again, except on windows. See the diff for conda-forge/google-cloud-cpp-feedstock@ae95a6d in conda-forge/google-cloud-cpp-feedstock#183

diff --git a/.scripts/build_steps.sh b/.scripts/build_steps.sh
index 4552b6d..e9a5f15 100755
--- a/.scripts/build_steps.sh
+++ b/.scripts/build_steps.sh
@@ -34,9 +34,9 @@ CONDARC
 export CONDA_LIBMAMBA_SOLVER_NO_CHANNELS_FROM_INSTALLED=1

 mamba install --update-specs --yes --quiet --channel conda-forge --strict-channel-priority \
-    pip mamba conda-build conda-forge-ci-setup=4 "conda-build>=24.1" "py-lief<0.14"
+    pip mamba conda-build conda-forge-ci-setup=4 python=3.11 py-lief=0.12.3
 mamba update --update-specs --yes --quiet --channel conda-forge --strict-channel-priority \
-    pip mamba conda-build conda-forge-ci-setup=4 "conda-build>=24.1" "py-lief<0.14"
+    pip mamba conda-build conda-forge-ci-setup=4 python=3.11 py-lief=0.12.3

 # set up the condarc
 setup_conda_rc "${FEEDSTOCK_ROOT}" "${RECIPE_ROOT}" "${CONFIG_FILE}"
diff --git a/.scripts/run_osx_build.sh b/.scripts/run_osx_build.sh
index 9904c13..a247ce4 100755
--- a/.scripts/run_osx_build.sh
+++ b/.scripts/run_osx_build.sh
@@ -26,9 +26,9 @@ export CONDA_SOLVER="libmamba"
 export CONDA_LIBMAMBA_SOLVER_NO_CHANNELS_FROM_INSTALLED=1

 mamba install --update-specs --quiet --yes --channel conda-forge --strict-channel-priority \
-    pip mamba conda-build conda-forge-ci-setup=4 "conda-build>=24.1" "py-lief<0.14"
+    pip mamba conda-build conda-forge-ci-setup=4 python=3.11 py-lief=0.12.3
 mamba update --update-specs --yes --quiet --channel conda-forge --strict-channel-priority \
-    pip mamba conda-build conda-forge-ci-setup=4 "conda-build>=24.1" "py-lief<0.14"
+    pip mamba conda-build conda-forge-ci-setup=4 python=3.11 py-lief=0.12.3



diff --git a/.scripts/run_win_build.bat b/.scripts/run_win_build.bat
index e7275f3..712b303 100755
--- a/.scripts/run_win_build.bat
+++ b/.scripts/run_win_build.bat
@@ -24,7 +24,7 @@ set "CONDA_LIBMAMBA_SOLVER_NO_CHANNELS_FROM_INSTALLED=1"

 :: Provision the necessary dependencies to build the recipe later
 echo Installing dependencies
-mamba.exe install "python=3.10" pip mamba conda-build conda-forge-ci-setup=4 "conda-build>=24.1" "py-lief<0.14" -c conda-forge --strict-channel-priority --yes
+mamba.exe install "python=3.10" pip mamba conda-build conda-forge-ci-setup=4 python=3.11 py-lief=0.12.3 -c conda-forge --strict-channel-priority --yes
 if !errorlevel! neq 0 exit /b !errorlevel!

 :: Set basic configuration

That's because the windows setup scripts are the only ones that contain a separate python version pin, which conflicts in this case. Remove the 3.10 pin so that this is uniform across platforms.

[beckermr]

We've had a pin on windows since azure was added. @mariusvniekerk did that work over half a decade ago. I am fine removing it, but I am curious if anyone knows why it was there in the first place.

[h-vetinari]

I think we should be able to try without big risks - I don't see why the behaviour would be different from the unix builds, where we don't have the pin either.

[beckermr]

Did you try a job explicitly without a pin or just a job with an updated pin?

[h-vetinari]

Did you try a job explicitly without a pin or just a job with an updated pin?

No I haven't but we can easily try.

[beckermr]

Let's try a job like that with a custom rerender using this branch. If that works, then I say we merge.

[h-vetinari]

Seems to be running fine in conda-forge/scipy-feedstock#284