From 141a66f9dea30c109a7fd75cbfe1dde6820799aa Mon Sep 17 00:00:00 2001 From: Amit Patankar Date: Wed, 7 Aug 2019 10:32:05 -0700 Subject: [PATCH] Install the new future module directly in the virtualenv when building and testing TensorFlow using pip_new.sh. PiperOrigin-RevId: 262165125 --- tensorflow/tools/ci_build/builds/pip_new.sh | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/tensorflow/tools/ci_build/builds/pip_new.sh b/tensorflow/tools/ci_build/builds/pip_new.sh index a38b10fdffe..72f1b582087 100755 --- a/tensorflow/tools/ci_build/builds/pip_new.sh +++ b/tensorflow/tools/ci_build/builds/pip_new.sh @@ -452,6 +452,12 @@ install_tensorflow_pip() { # ImportError: cannot import name py31compat ${PIP_BIN_PATH} install --upgrade setuptools==39.1.0 || \ die "Error: setuptools install, upgrade FAILED" + + # Install the future package in the virtualenv. Installing it in user system + # packages does not appear to port it over when creating a virtualenv. + # ImportError: No module named builtins + ${PIP_BIN_PATH} install --upgrade "future>=0.17.1" || \ + die "Error: future install, upgrade FAILED" } run_test_with_bazel() {