About google-cloud-language

Home: https://github.com/googleapis/google-cloud-python

Package license: Apache 2.0

Feedstock license: BSD 3-Clause

Summary: Python Client for Google Cloud Natural Language

Python Client for Google Cloud Natural Language

The Google Cloud Natural Language API can be used to reveal the
structure and meaning of text via powerful machine
learning models. You can use it to extract information about
people, places, events and much more, mentioned in text documents,
news articles or blog posts. You can use it to understand
sentiment about your product on social media or parse intent from
customer conversations happening in a call center or a messaging
app. You can analyze text uploaded in your request or integrate
with your document storage on Google Cloud Storage.

note

This library currently does not run on Google App Engine Standard.
We are actively working on adding this support.

Quick Start

In order to use this library, you first need to go through the following steps:

Supported Python Versions

Python >= 3.5

Deprecated Python Versions

Python == 2.7. Python 2.7 support will be removed on January 1, 2020.

Current build status

Azure

Variant	Status
linux_python2.7
linux_python3.6
linux_python3.7
linux_python3.8
osx_python2.7
osx_python3.6
osx_python3.7
osx_python3.8
win_python3.6vc14
win_python3.7vc14
win_python3.8vc14

Linux_ppc64le

Current release info

Name	Downloads	Version	Platforms

Installing google-cloud-language

Installing google-cloud-language from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge

Once the conda-forge channel has been enabled, google-cloud-language can be installed with:

conda install google-cloud-language

It is possible to list all of the versions of google-cloud-language available on your platform with:

conda search google-cloud-language --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages.
In order to provide high-quality builds, the process has been automated into the
conda-forge GitHub organization. The conda-forge organization contains one repository
for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build
the package) and the necessary configurations for automatic building using freely
available continuous integration services. Thanks to the awesome service provided by
CircleCI, AppVeyor
and TravisCI it is possible to build and upload installable
packages to the conda-forge
Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance
conda-smithy has been developed.
Using the conda-forge.yml within this repository, it is possible to re-render all of
this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock.
Its primary use is in the construction of the CI .yml files
and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to
produce the finished article (built conda distributions)

Updating google-cloud-language-feedstock

If you would like to improve the google-cloud-language recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
conda-forge channel, whereupon the built conda packages will be available for
everybody to install and use from the conda-forge channel.
Note that all branches in the conda-forge/google-cloud-language-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.

In order to produce a uniquely identifiable distribution:

If the version of a package is not being increased, please add or increase
the build/number.
If the version of a package is being increased, please remember to return
the build/number
back to 0.

Feedstock Maintainers

@BrentDorsey

parthea/google-cloud-language-feedstock