TensorFlow's EasyBlock installs the produced wheel package via
pip install --ignore-installed
|
cmd = "pip install --ignore-installed --prefix=%s %s" % (self.installdir, whl_paths[0]) |
As a consequence, it pulls in binary wheels of all dependencies, including for example NumPy. So loading the TensorFlow module will replace the NumPy as part of the Python package (linked against MKL in my case) with a precompiled NumPy linked against a pre-shipped OpenBLAS. Is this intended behavior?
At least on our systems, removing --ignore-installed leads to desired behavior, i.e. pip does not install those dependencies that were already satisfied via dependent modules.
TensorFlow's EasyBlock installs the produced wheel package via
pip install --ignore-installedeasybuild-easyblocks/easybuild/easyblocks/t/tensorflow.py
Line 372 in 4f81668
As a consequence, it pulls in binary wheels of all dependencies, including for example NumPy. So loading the TensorFlow module will replace the NumPy as part of the Python package (linked against MKL in my case) with a precompiled NumPy linked against a pre-shipped OpenBLAS. Is this intended behavior?
At least on our systems, removing
--ignore-installedleads to desired behavior, i.e. pip does not install those dependencies that were already satisfied via dependent modules.