From d7790efc8e56ab3b3142dd4147d685c10b81b7a5 Mon Sep 17 00:00:00 2001 From: Matt Kwong Date: Thu, 5 Apr 2018 13:00:28 -0700 Subject: Unpin pip version installed in build_python.sh Fix for issue #14815. Pinning to 9.0.3 doesn't work because pip fails to recognize that as a valid version. Newer versions of pip have a fallback on macOS to use SecureTransport instead of their outdated OpenSSL that doesn't support TLSv1.2. --- tools/run_tests/helper_scripts/build_python.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/run_tests/helper_scripts/build_python.sh b/tools/run_tests/helper_scripts/build_python.sh index dac29b91dd..e6d0fdf7e4 100755 --- a/tools/run_tests/helper_scripts/build_python.sh +++ b/tools/run_tests/helper_scripts/build_python.sh @@ -132,7 +132,7 @@ fi # Perform build operations # ############################ -# Instnatiate the virtualenv, preferring to do so from the relevant python +# Instantiate the virtualenv, preferring to do so from the relevant python # version. Even if these commands fail (e.g. on Windows due to name conflicts) # it's possible that the virtualenv is still usable and we trust the tester to # be able to 'figure it out' instead of us e.g. doing potentially expensive and @@ -158,7 +158,7 @@ case "$VENV" in ;; esac -$VENV_PYTHON -m pip install --upgrade pip==9.0.1 +$VENV_PYTHON -m pip install --upgrade pip $VENV_PYTHON -m pip install setuptools $VENV_PYTHON -m pip install cython $VENV_PYTHON -m pip install six enum34 protobuf futures -- cgit v1.2.3