-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Pubsub: clients emit pending deprecation warnings #6887
Copy link
Copy link
Closed
Labels
api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Metadata
Metadata
Assignees
Labels
api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Type
Fields
Give feedbackNo fields configured for issues without a type.
(See Google Group )
With the Python pubsub package v 0.39.0, a simple call to pubsub_v1.SubscriberClient() gives warnings from deep in Google code
This apparently incorrect channel is created inside Google code, e.g.
google.cloud.pubsub_v1.subscriber.client.Client#__init__Although keeping ahead of deprecation can be challenging, Google's own code should avoid warnings and do whatever Google says is the official way.