Hello, Starting today, running a beam pipeline triggers a large reinstallation of python modules. For some reason, it forces full rebuilds from source - since beam depends on numpy, this takes a long time.
There's nothing strange about my python setup. I'm using python3.7 on debian buster with the dataflow runner. My venv is setup like this: python3 -m venv ~/.venvs/beam . ~/.venvs/beam/bin/activate python3 -m pip install --upgrade wheel python3 -m pip install --upgrade pip setuptools python3 -m pip install -r requirements.txt My requirements.txt has: apache-beam[gcp]==2.23.0 boto3==1.15.0 When it's building, `ps ax | grep python` shows me this: /home/ross/.venvs/beam/bin/python -m pip download --dest /tmp/dataflow- requirements-cache -r requirements.txt --exists-action i --no-binary :all: How do I prevent this? It's far too slow to develop with, and our compliance folks are likely to prohibit a tool that silently downloads & builds unknown code. Ross
