-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Improve packaging for Google Cloud Python Clients #11184
Comments
Hi @thclark, Thanks for raising this issue and sharing feedback about providing a better user experience. I'll discuss the feedback internally and create feature requests as we identify them. Please also share feature requests using this link. Regarding the deprecation notice, there are no usages of |
Hi all! Ran into this issue as well, is there a timeline for fixing this issue? I saw that it has priority P2, does that translate to a time span? |
As a workaround for the deprecation warning, you can set a warning filter (see ibis-project/ibis#5980) |
Thanks, I added the following to ignore the warnings
|
Waiting for the next gapic-generator release: googleapis/gapic-generator-python#1860 |
Upgrading to google-api-core 2.15.0 seems to have resolved the deprecation warnings in 3.11 for us (although we are not the reporter). |
I'm getting a lot of deprecation warnings, because the explicit declaration of package namespaces via
pkg_resources
is deprecated.Rather than make an issue about just that I think it's better to look at the wider problem: that this is a bizarre way to set up a group of very closely related python packages. It causes:
Please can the google cloud client packaging be architected more straightforwardly? I'd recommend using a single package and specifying optional extras with the
[extras]
ability - this is exactly the use case for that funcitonality that the python packaging maintainers envisaged.This would be a revelation in how easy it is to use the python client and manage dependencies, I'm sure it'd lead to stronger uptake of GCP overall from people driving it via python.
Current state of the different platforms
In AWS
poetry add boto3
In GCP
Deprecations that motivated me to start this issue
The messages that led to this particular issue (these arise for the libs that I use, I assume it's the same across the board for all packages):
The text was updated successfully, but these errors were encountered: