Install a fake local grpc-google-iam-v1 to resolve the version conflict.#2457
Install a fake local grpc-google-iam-v1 to resolve the version conflict.#2457
grpc-google-iam-v1 to resolve the version conflict.#2457Conversation
|
@dhermes not sure - what does pip say is the collected and installed packages when you do it? |
|
@bjwatson it's pretty easy to support a wide range of oauth2client versions, any reason to keep the bounds so tight? |
|
Only failure was Just added @tseaver Any issues with merging this while we wait for the version conflict to be resolved? |
388b9bf to
5689be5
Compare
|
@jonparrott Paranoia, per semver. I can relax it. What do you suggest? |
|
Best closed PR ever! I just manually rebuilt |
See https://readthedocs.org/projects/google-cloud-python/builds/4449660/ for validation of this fact (at 388b9bf). This is a temporary hack to workaround the fact that the latest (0.10.1)
gapic-google-pubsub-v1relies ongrpc-google-iam-v10.10.0, but they have contradicting bounds onoauth2client:'oauth2client>=1.4.11, <2.0.0',ingrpc-google-iam-v1'oauth2client>=3.0.0, <4.0.0dev',ingapic-google-pubsub-v1Fixes #2405.
WORTH NOTING: I am sending the PR from a branch I created on
GoogleCloudPlatform. I created it here so I could test if the hack worked on RTD without having to keep behaving badly with premature merges./cc @bjwatson
ASIDE: @tseaver @jonparrott Any idea why
pipis cool with the version conflict butsetuptoolsisn't? (Evidence:python setup.py installfails at the "Processing dependencies" step with the conflict described above, butpipis happy to let it happen.)