Re-vendor / cleanup apitools as used in storage · Issue #1186 · googleapis/google-cloud-python · GitHub

8000 Re-vendor / cleanup apitools as used in storage · Issue #1186 · googleapis/google-cloud-python · GitHub

Re-vendor / cleanup apitools as used in storage #1186

Closed

Closed

Re-vendor / cleanup apitools as used in storage#1186

Assignees

Labels

api: bigqueryapi: storagepackaging

opened

on Oct 15, 2015

Work plan:

Pull in the subset we use as a non-temporary fork (e..g, gcloud._apitools). #1186: Revendor apitools as 'gcloud._apitools' #1189
Get it to 100% unit test coverage using our normal testing style. Coverage for 'gcloud._apitools.util' #1190, Coverage for 'gcloud._apitools.exceptions' #1191, Coverage for 'gcloud._apitools.exceptions' #1191, Coverage for 'gcloud._apitools.buffered_stream' #1192, Coverage for 'gcloud._apitools.stream_slice' #1193, Coverage for 'gcloud._apitools.http_wrapper' #1196, Add coverage for 'gcloud._apitools.transfer' #1207
Rename it gcloud.streaming so nose finds its tests. Rename 'gcloud/_apitools' -> 'gcloud/streaming' #1208
Remove unused bits. Streaming: strip unused features #1209
Make it fit our coding standards. Streaming: add pep8 / pylint goodness #1210

Metadata

Assignees

tseaver

Labels

api: bigqueryapi: storagepackaging

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

0