You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the latest pip version where the default dependency resolver changed, and there are some issues installing google-cloud-aiplatform alongside apache-beam due to incompatible versions of mock.
(env) ➜ python --version
Python 3.8.5
(env) ➜ pip --version
pip 20.3.3 from /usr/local/google/home/dcavazos/src/sandbox/env/lib/python3.8/site-packages/pip (python 3.8)
(env) ➜ pip install apache-beam==2.27.0 google-cloud-aiplatform==0.4.0
# Installation fails after a very long time
I searched through the python-aiplatform repo and mock is only used for testing, so it could safely be part of tests_require instead of install_requires in the setup.py file.
The mock dependency should also be a part of the tests_require in Apache Beam as well, but due to BEAM-8840 the setup_requires and tests_require sections were removed.
Using an older version of pip like 20.2.* throws an error/warning, but the installation still succeeds.
# This error/warning shows when using pip 20.2.4, both packages can still be installed.
ERROR: google-cloud-aiplatform 0.4.0 has requirement mock>=4.0.2, but you'll have mock 2.0.0 which is incompatible.
Starting with pip 20.3, the new dependency resolver cannot install both libraries together due to the mock versions incompatibility.
Environment details
OS type and version: Linux 5.7.17-1rodete4-amd64 #1 SMP Debian 5.7.17-1rodete4 (2020-10-01) x86_64
Python version: Python 3.8.5
pip version: pip 20.3.3 from /usr/local/google/home/dcavazos/src/sandbox/env/lib/python3.8/site-packages/pip (python 3.8)
google-cloud-aiplatform version: 0.4.0 but cannot be installed alongside apache-beam==2.27.0
Steps to reproduce
Update pip to the latest version.
pip install -U pip
Install apache-beam and google-cloud-aiplatform (it takes a really long time to resolve dependencies as well, but that's out of the scope for this).
In the setup.py file, create a new section called tests_require and move the mock dependency to it.
Workaround
In the meantime, the only workaround is to force downgrading your pip version before installing your requirements, which is not always possible in some managed services.
Hi,
I'm using the latest
pip
version where the default dependency resolver changed, and there are some issues installinggoogle-cloud-aiplatform
alongsideapache-beam
due to incompatible versions ofmock
.(env) ➜ python --version Python 3.8.5 (env) ➜ pip --version pip 20.3.3 from /usr/local/google/home/dcavazos/src/sandbox/env/lib/python3.8/site-packages/pip (python 3.8) (env) ➜ pip install apache-beam==2.27.0 google-cloud-aiplatform==0.4.0 # Installation fails after a very long time
I searched through the
python-aiplatform
repo andmock
is only used for testing, so it could safely be part oftests_require
instead ofinstall_requires
in thesetup.py
file.The
mock
dependency should also be a part of thetests_require
in Apache Beam as well, but due to BEAM-8840 thesetup_requires
andtests_require
sections were removed.Using an older version of
pip
like20.2.*
throws an error/warning, but the installation still succeeds.Starting with
pip 20.3
, the new dependency resolver cannot install both libraries together due to themock
versions incompatibility.Environment details
Linux 5.7.17-1rodete4-amd64 #1 SMP Debian 5.7.17-1rodete4 (2020-10-01) x86_64
Python 3.8.5
pip 20.3.3 from /usr/local/google/home/dcavazos/src/sandbox/env/lib/python3.8/site-packages/pip (python 3.8)
google-cloud-aiplatform
version:0.4.0
but cannot be installed alongsideapache-beam==2.27.0
Steps to reproduce
Update
pip
to the latest version.Install
apache-beam
andgoogle-cloud-aiplatform
(it takes a really long time to resolve dependencies as well, but that's out of the scope for this).Suggested fix
In the
setup.py
file, create a new section calledtests_require
and move themock
dependency to it.Workaround
In the meantime, the only workaround is to force downgrading your
pip
version before installing your requirements, which is not always possible in some managed services.pip install -U pip=='20.2.*' pip install -r requirements.txt
The text was updated successfully, but these errors were encountered: