GAX support: need new releases of 'google-gax' and 'gax-google-pubsub-v1'

[tseaver]

I'm blocked on finishing / pushing my GAX pubsub changes on new releases. See:

• https://pypi.python.org/pypi/google-gax
• https://pypi.python.org/pypi/gax-google-pubsub-v1

CC @tbetbetbe

[tbetbetbe]

Sorry - these were due last week - I could not get to them before I moved.
The new ETA is this time tomorrow.

On 24 May 2016 at 00:50, Tres Seaver notifications@github.com wrote:

I'm blocked on finishing / pushing my GAX pubsub changes on new releases.
See:

• https://pypi.python.org/pypi/google-gax
• https://pypi.python.org/pypi/gax-google-pubsub-v1

CC @tbetbetbe https://github.com/tbetbetbe

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1814

This email may be confidential or privileged. If you received this
communication by mistake, please don't forward it to anyone else (it may
contain confidential or privileged information), please erase all copies of
it, including all attachments, and please let the sender know it went to
the wrong person. Thanks.

[tseaver]

@tbetbetbe can you update the ETA?

[tbetbetbe]

Sorry about the delay on this. As of now, this is my highest priority
task, I'll update this thread within the next day to report completion.

On 25 May 2016 at 13:18, Tres Seaver notifications@github.com wrote:

@tbetbetbe https://github.com/tbetbetbe can you update the ETA?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1814 (comment)

This email may be confidential or privileged. If you received this
communication by mistake, please don't forward it to anyone else (it may
contain confidential or privileged information), please erase all copies of
it, including all attachments, and please let the sender know it went to
the wrong person. Thanks.

[tseaver]

@tbetbetbe Any update?

[tseaver]

Looks like we have a new release of google-gax. We still need another release of gax-google-pubsub-v1, as well as an initial release of gax-google-logging-v2.

[tseaver]

Doesn't look as though the tag for gax-python 0.11.0 has been pushed to Github yet.

[tseaver]

Doesn't look as though the tag for gax-python 0.11.0 has been pushed to Github yet.

I see the v0.11.0 tag now.

@tbetbetbe are releases for the (generated, I presume) gax-google-pubsub-v1 and gax-google-logging-v2 libraries pending something in the upstream? The protos haven't changed recently AFAIK. The generation is done via https://github.com/googleapis/toolkit, right?

[tbetbetbe]

That's correct.

What I'm trying to do is make sure that their
dependencies, grpc-google-pubsub-v1 and grpc-google-logging-v2 are updated
first.
These are not generated by toolkit, rather they are generated by protoc +
the grpc python plugin. That's been updated, and I want to make sure that
we use the updated version.

On 6 June 2016 at 21:22, Tres Seaver notifications@github.com wrote:

Doesn't look as though the tag for gax-python 0.11.0 has been pushed to
Github yet.

I see the v0.11.0 tag
https://github.com/googleapis/gax-python/releases/tag/v0.11.0 now.

@tbetbetbe https://github.com/tbetbetbe are releases for the
(generated, I presume) gax-google-pubsub-v1 and gax-google-logging-v2
libraries pending something in the upstream? The protos haven't changed
recently AFAIK. The generation is done via https://github.com/googleapis/
toolkit, right?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1814 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AI18Fhpm_YonsgU4K5PjTbK_LUqqTBHKks5qJHOPgaJpZM4IkoFY
.

This email may be confidential or privileged. If you received this
communication by mistake, please don't forward it to anyone else (it may
contain confidential or privileged information), please erase all copies of
it, including all attachments, and please let the sender know it went to
the wrong person. Thanks.

[tbetbetbe]

@jmuk, can you finish this off please, after submitting googleapis/packman#40 ?

I've successfully updated/published the following

• grpc-google-pubsub-v1
• grpc-google-logging-v2
• grpc-google-devtools-cloudtrace-v1

Now, they all depend on grpcio-v0.14.0 and are generated with the latest grpc python plugin, which fixes issues some python package users are seeing where there are missing imports. (FYI: @jgeiger)

I think the best route would be to submit googleapis/artman#23, and use the changes it contains to use artman to create the updated grpc-gax packages.

The created packages can be submitted using the googleapis-package user name.

[jmuk]

Well, it turns out that googleapis/artman#23 is not useful by itself for now. Without googleapis/gapic-generator#126, the automatically generated whl file will have the config .json files at a wrong place.

[jmuk]

now googleapis/artman#23 is merged, FYI

[tseaver]

Yay! It looks as though googleapis/gapic-generator#192 has landed as well (resolving googleapis/gapic-generator#126, AFAICT).