Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove pubsub and logging as namespace packages #2258

Closed
dhermes opened this issue Sep 7, 2016 · 18 comments
Closed

Remove pubsub and logging as namespace packages #2258

dhermes opened this issue Sep 7, 2016 · 18 comments
Assignees
Labels
api: logging Issues related to the Cloud Logging API. api: pubsub Issues related to the Pub/Sub API. packaging

Comments

@dhermes
Copy link
Contributor

dhermes commented Sep 7, 2016

This should be assigned to @bjwatson but I can't assign to him in this repo.

Blocking on having the GAX generated Pub / Sub and Logging clients no longer use google.cloud.logging and google.cloud.pubsub as namespace packages.

@dhermes dhermes added packaging api: pubsub Issues related to the Pub/Sub API. api: logging Issues related to the Cloud Logging API. GAX labels Sep 7, 2016
@dhermes dhermes self-assigned this Sep 7, 2016
@bjwatson
Copy link

bjwatson commented Sep 7, 2016

If the admin for GoogleCloudPlatform adds me, then you can assign away. :) (FYI, @omaray and @jgeewax)

I'm just resolving the email thread that you're copied on for correct package naming. After that, it's pretty easy to re-generate these surfaces, since they've already been thoroughly tested (a simple diff will tell me they still look good).

@theacodes
Copy link
Contributor

I can add you to this repo, @elibixby can add you to the veneer team.

@theacodes
Copy link
Contributor

Invitation sent.

@bjwatson
Copy link

bjwatson commented Sep 7, 2016

Thanks @jonparrott

@bjwatson bjwatson self-assigned this Sep 7, 2016
@dhermes
Copy link
Contributor Author

dhermes commented Sep 7, 2016

I'm just resolving the email thread that you're copied on for correct package naming. After that, it's pretty easy to re-generate these surfaces, since they've already been thoroughly tested

Yup. Just wanted to have this as a placeholder

@bjwatson
Copy link

bjwatson commented Sep 7, 2016

Awesome, thanks Danny.

@bjwatson
Copy link

bjwatson commented Sep 13, 2016

@dhermes I published 0.9.0 to https://testpypi.python.org/pypi/ for Pub/Sub, Logging, Vision, and Language (both gRPC and GAX).

I did a little testing with Vision, and ran into the same AttributeError: 'grpc._cython.cygrpc.Channel' object has no attribute 'unary_unary' that I did for Speech v1beta1 a couple weeks ago. I'll keep testing and refining more tomorrow.

BTW, the gRPC path changes for Vision required a small hand-edit to the image_annotator_pb2.py file (fixing an import statement for geometry_pb2.py). We're going to have to figure out if we can automate this or fix it upstream in the Python proto generator, or it will be non-maintainable as auto-gen code.

@dhermes
Copy link
Contributor Author

dhermes commented Sep 13, 2016

Thanks for the update.

@bjwatson
Copy link

@dhermes As it turns out, the AttributeError: 'grpc._cython.cygrpc.Channel' object has no attribute 'unary_unary' error is due to googleapis/gax-python#127. When I use google-gax 0.12.5 (which does not have this change), the error goes away and Cloud Vision works perfectly.

I discussed with @geigerj, and there's more work we need to do to fully remove grpc.beta. The problem is that google-gax is fixed, but our GAPIC generated code still references the grpc.beta code. The error above is because grpc and grpc.beta use different default channels.

We have two options to move forward:

  1. I'll generate the GAPIC code for google-gax 0.12.5, which will still use grpc.beta. I think I can get this done tonight, but it means you won't have Remove beta from gRPC imports gax-python#126 in your next release.
  2. We remove grpc.beta from our autogen code. Jacob estimates that this will take most of tomorrow to finish, so we'll be delayed by at least a day with this option.

What's your preference?

@dhermes
Copy link
Contributor Author

dhermes commented Sep 15, 2016

My preference is that we dump grpc.beta, so we can wait for releases that do the same.

@bjwatson
Copy link

Ok, we will start work on that immediately. FYI @geigerj

@dhermes
Copy link
Contributor Author

dhermes commented Sep 15, 2016

Thanks.

@bjwatson
Copy link

Latest versions referenced in #2324

BTW, when will the ML APIs start being used? (Vision, Language)

@dhermes
Copy link
Contributor Author

dhermes commented Sep 16, 2016

@bjwatson I didn't realize language was generated yet. I can do that ASAP. Pointer to PyPI links?

@daspecster
Copy link
Contributor

daspecster commented Sep 16, 2016

@bjwatson
Copy link

@daspecster @dhermes That's correct.

@dhermes dhermes reopened this Sep 16, 2016
@dhermes
Copy link
Contributor Author

dhermes commented Sep 16, 2016

Still need to remove the namespace package bits. On it now.

@bjwatson
Copy link

@daspecster @dhermes FYI, this has the updated links: googleapis/googleapis#140

dhermes added a commit to dhermes/google-cloud-python that referenced this issue Sep 16, 2016
dhermes added a commit to dhermes/google-cloud-python that referenced this issue Sep 16, 2016
parthea pushed a commit that referenced this issue Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: logging Issues related to the Cloud Logging API. api: pubsub Issues related to the Pub/Sub API. packaging
Projects
None yet
Development

No branches or pull requests

4 participants