-
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
Tracking namespace change #1978
Comments
Is this in reference to changing to |
@jonparrott yup! I wasn't sure if that was finalized or not. |
@jgeewax can confirm, but from what I understand that is the way we want to go. |
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. |
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 |
@omaray I held off on grabbing the equivalents for |
@dhermes you can use underscores but it's preferable to use
|
Thanks @jonparrott. @tseaver @jgeewax @omaray, shall we use |
|
👍 Just created https://pypi.python.org/pypi/google-cloud-core |
Just created https://pypi.python.org/pypi/google-cloud-happybase for #1762 |
Thanks @dhermes. All sgtm. Not sure if we added speech, vision, and language - but I guess might as well. |
@omaray Just created https://pypi.python.org/pypi/google-cloud-vision and https://pypi.python.org/pypi/google-cloud-speech Should it be called |
+1 for |
So Ruby and Node.js called it google-cloud-language: Example: https://www.npmjs.com/package/@google-cloud/language It's shorter indeed. If it's easy to do, let's hold both! I'll check with the team. |
It is easy but that would just be namespace squatting on PyPI; seems like it would be frowned upon. Though on the flipside, non-Google entities squatting on a name with I've noticed the Googlers keep calling it Language but that seems to be vague for people not already familiar with the API. |
It's fine to have both (fyi, if we do run into a case where there's someone squatting on our name we can get that resolved). |
So @jonparrott as packaging wizard your opinion is that I should grab both (a) and we should publish to both (b)? |
Grab both and publish to one, and publish a metapackage to the other. But only if you feel like it's really necessary. I'd say don't. Just go with |
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 |
@tseaver @omaray (and anyone else who likes to weigh in) are we a go to grab
i.e. some of these it's unclear if they deserve their own package / are priorities. @rimey any preference for grabbing |
I think those are fine. AFAICT, the |
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 |
Yes, confirmed. We are sticking with google-cloud-{api} |
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-cloud
google-cloud-core
google-cloud-datastore
google-cloud-storage
google-cloud-pubsub
google-cloud-bigquery
google-cloud-bigtable
google-cloud-happybase
google-cloud-logging
google-cloud-vision
google-cloud-speech
google-cloud-language
(and the aliasgoogle-cloud-natural-language
)google-cloud-resource-manager
google-cloud-translate
google-cloud-dns
google-cloud-monitoring
google-cloud-error-reporting
The text was updated successfully, but these errors were encountered: