GCloud dependency conflicts

[googleapis]

GCloud dependency conflicts

[geigerj]

Note: workaround is to manually manage the installed version with pip

(venv) $ pip uninstall {conflicting package}
(venv) $ pip install {conflicting package}=={non-conflicting version}

[dhermes]

This is a known issue but google-cloud-python has now been released (version 0.19.0)

I am AFK right now so can't find the issue but @geigerj mentioned in our bug tracker that 0.18.2 wouldn't be necessary in light of 0.19.0

[bjwatson]

@dhermes I think we're realizing in hindsight that this small 0.18.2 release would help the transition that was created by us doing two rename simultaneously: gcloud -> google-cloud and gax-google-* -> gapic-google-*.

[dhermes]

Since this is "our" issue I opened #2385 as well (for record-keeping). This release seems to be more trouble than it's worth.

[bjwatson]

Thanks, Danny. @geigerj or I will test that this bug is no longer occurring, and then close this issue.

[bjwatson]

This is all due to lacking upper bounds on dependencies in our code as well as yours. We just need to tighten this up going forward, so that we're enforcing semver (including the variant we agreed to for 0.x).

[bjwatson]

@dhermes Could I trouble you to release gcloud 0.18.3 with the google-gax upper-bound tightened to 0.13dev? I don't think that gax-google-* 0.8.x is compatible with google-gax 0.13.0, due to moving away from the gRPC beta methods in the latter (the former did not do this until gapic-google-* 0.9.x).

[dhermes]

@bjwatson Does it matter? We already have 0.19.0 released. This is a lot of churn for 0.x versions

[bjwatson]

It's because our self-service instructions are broken for our partners due to artman still depending on gcloud. There's more work we need to do to port it to google-cloud: #101

It seems fastest to just fix the upper bounds in gcloud 0.18.x, so that we can keep focusing on churning out APIs before the end of the quarter.

[dhermes]

1. OK doing it now
2. Please fix your self-service instructions instead of punting back to us

---

Pushed the tag, canceled the build since it won't push to PyPI anyway and Travis is being slow these days. The only relevant commit makes the upper bound tighter. Manually uploaded to PyPI with twine.

[bjwatson]

@dhermes Thanks for pushing the new release.

Just for the record, the problem wasn't with our instructions. It was with upgrading our tool's dependency from gcloud 0.18.x to google-cloud 0.19.x, which apparently is not trivial (#101). We'll need to do it eventually anyway, but I was thinking that fixing the dependency upper bounds in gcloud 0.18.x was a more expedient solution. Sorry it required two passes.

[bjwatson]

Confirmed that this issue is now fixed.