commit | fd093c6704cd6c2cc18ba107d7a6f6d09a95f8b1 | [log] [tgz] |
---|---|---|
author | Robert Spier <rspier@google.com> | Wed Dec 20 12:28:43 2017 -0800 |
committer | Robert Spier <rspier@google.com> | Wed Dec 20 12:28:43 2017 -0800 |
tree | 37492275f72a3b927b68296b19505e5f84fb7f38 | |
parent | 4b42da3061c9871bbbc14b504f3d8c0203451325 [diff] |
Add .editorconfig to mostly do the right thing with formatting.
API Documentation is at https://developers.google.com/open-source/gci/api
./list_tasks.py --apikey APIKEY
./list_instances.py --apikey APIKEY
./csv_uploader.py --apikey APIKEY file.csv
Each script also supports other flags. Use --help to see them.
The client library requires requests to be installed.
You can install it with pip
or easy_install
(instructions) or install your operating system specific package. On Ubuntu or Debian, it is in the python-requests
package.
Organization Adminstrators can find their API key on their User Profile.
We follow the Google Python Style Guide with a few modifications to match the Google internal version. The primary one is the use of 2 space indents.
Use yapf to keep the code formatted nicely. You can set up an auto-save hook in your editor, or run it manually:
# one time setup: pip install yapf # format files: yapf -i *.py
To report bugs, please email gci-support@google.com.