Makinggrpcio-gcp a hard dependency ofgoogle-cloud-spanner seems like it involves some risk: I don't know how well that package is supported across all the platforms, but for instance thelatest version has a Python2-only wheel as its only binary distribution. I can't find its repository, either.

/cc@snehashah16

I'm going to send a PR to fix the wheel situation, then we can merge this.

The repo is athttps://github.com/GoogleCloudPlatform/grpc-gcp-python

Universal wheel PR:GoogleCloudPlatform/grpc-gcp-python#99

Updated the min version for api_core and published universal wheel package for grpcio-gcp.

As for the release version for api-core and cloud-spanner, should I bump their versions now in this PR, or leave them for you guys when they are ready to release?

No, releasetool will handle that.

Thanks! So the next step would be just to release api-core and cloud-spanner, right?

We can't get tests passing for this PR untilapi_core/setup.py has the new version number.

I think we should separate this into 2 pr, one for api core and another one for spanner. So we can release api core before spanner, correct?

@WeiranFang This PR already touchesapi_core/setup.py: it just needs to bump the version number there so that the constraint inspanner/setup.py is satisfied.@theacodes will make the releases for the two in the order you suggest, but we can't merge without getting the tests passing first.

I see, thanks for the clarification!