Repository navigation
Tracking namespace change #1978
Description
Here's a place we can track updates to the future changing of the gcloud-python namespace.
This change could break things in the future.
Sub-projects already partially created:
google-cloudgoogle-cloud-coregoogle-cloud-datastoregoogle-cloud-storagegoogle-cloud-pubsubgoogle-cloud-bigquerygoogle-cloud-bigtablegoogle-cloud-happybasegoogle-cloud-logginggoogle-cloud-visiongoogle-cloud-speechgoogle-cloud-language(and the aliasgoogle-cloud-natural-language)google-cloud-resource-managergoogle-cloud-translategoogle-cloud-dnsgoogle-cloud-monitoringgoogle-cloud-error-reporting
Activity
theacodes commentedon Jul 12, 2016
Is this in reference to changing to
google.cloud?daspecster commentedon Jul 12, 2016
@jonparrott yup! I wasn't sure if that was finalized or not.
theacodes commentedon Jul 12, 2016
@jgeewax can confirm, but from what I understand that is the way we want to go.
daspecster commentedon Jul 22, 2016
We will want to update the User-Agent string as well for this right? Are there any other implications to that? i.e. people have that user-agent allowed in their apps/firewall.
jgeewax commentedon Jul 26, 2016
Let's leave the useragent string alone -- we would have a whole heap of stuff to fix if we change that....
Otherwise -- yes, we're definitely going forward with google.cloud as the import path
dhermes commentedon Aug 15, 2016
Using the form I created
with the
gcloudpypiaccount on PyPI.dhermes commentedon Aug 15, 2016
@omaray I held off on grabbing the equivalents for
dns,error_reporting,monitoring,resource_managerandtranslate, but I can do that as well if you like. I'm not sure if underscores are allowed in PyPI package names?theacodes commentedon Aug 15, 2016
@dhermes you can use underscores but it's preferable to use
-for consistency.google-cloud-error-reportingreads better thangoogle-cloud-error_reporting, even if the import path isgoogle.cloud.error_reporting.dhermes commentedon Aug 16, 2016
Thanks @jonparrott.
@tseaver @jgeewax @omaray, shall we use
google-cloud-corefor the code shared by allmodulessub-packages?tseaver commentedon Aug 16, 2016
google-cloud-coreSGTM.dhermes commentedon Aug 16, 2016
👍 Just created https://pypi.python.org/pypi/google-cloud-core
dhermes commentedon Aug 17, 2016
Just created https://pypi.python.org/pypi/google-cloud-happybase for #1762
omaray commentedon Aug 17, 2016
Thanks @dhermes. All sgtm. Not sure if we added speech, vision, and language - but I guess might as well.
7 remaining items
dhermes commentedon Aug 18, 2016
Cool. Thanks (I love having a packaging authority person to consult with...as an authority). Grabbed https://pypi.python.org/pypi/google-cloud-language and https://pypi.python.org/pypi/google-cloud-natural-language
dhermes commentedon Aug 18, 2016
@tseaver @omaray (and anyone else who likes to weigh in) are we a go to grab
google-cloud-dnsgoogle-cloud-error-reportinggoogle-cloud-monitoringgoogle-cloud-resource-managergoogle-cloud-translatei.e. some of these it's unclear if they deserve their own package / are priorities.
@rimey any preference for grabbing
google-cloud-monitoringorgoogle-cloud-stackdriver-monitoringor something else (or both, as we did withlanguage/natural-languageabove)tseaver commentedon Aug 19, 2016
I think those are fine. AFAICT, the
-stackdriverbit should be a replacement for-cloudif we are going to use it: (the branding seems confused to me).dhermes commentedon Aug 19, 2016
@rimey and @omaray can you weigh in as well?
omaray commentedon Aug 22, 2016
Yeah, so the whole Stackdriver branding can indeed be confusing. I need to get back to you on that one. For the time being, everything will be
google-cloud-{api}.omaray commentedon Sep 1, 2016
Yes, confirmed. We are sticking with google-cloud-{api}
docs: add short mode query sample & test (#1978)
feat: Add ML code samples from dbt blog post (#1978)
docs: migrate code from googleapis/python-bigquery (#18303)