python release v3.0.0b2.post1 breaks gcloud-python

[xfxyjwf]

See: googleapis/google-cloud-python#1570

Probable cause: 786f80f#commitcomment-16491845

@haberman @silviulica

[haberman]

Closing in favor of: #1296

[xfxyjwf]

Should we hide/remove v3.0.0b2.post1 from pypi as it may break some protobuf users?

[theacodes]

@xfxyjwf I would prefer it if you did that or cut a new release to fix, as it will take some time for me to update all of our samples to point to gcloud-python==0.11.0 and currently mostly lower versions will be broken.

[silviulica]

Feng/Josh I am ready to hide the 3.0.0b2.post1 release. We certainly need to understand better what is happening before unhiding. Just want one more team member to be aware of this before I actually do it. So I will wait today for a green light. In the meantime I am investigating root causes.

[haberman]

Yes @silviulica please feel free to go ahead on hiding the broken release.

[silviulica]

done

On Sat, Mar 5, 2016 at 1:30 PM, Joshua Haberman [email protected]
wrote:

Yes @silviulica https://github.com/silviulica please feel free to go
ahead on hiding the broken release.

—
Reply to this email directly or view it on GitHub
#1294 (comment).