Skip to content

Conversation

@craigcitro
Copy link
Contributor

As discovered in
googleapis/google-cloud-python#1760, we were
mangling bytes when encoding them as part of a multipart upload request. The
fix is to switch from using six.StringIO to six.BytesIO in transfer.py.
The patch here is closely based on
googleapis/google-cloud-python#1779.

PTAL @thobrla

cc @dhermes -- Danny, if you have two minutes to take a look at the test, I would love a set of more-python3-savvy eyes. It fails before the patch and passes after, so it's definitely testing the right things, but I would be willing to believe I've managed to fool myself. 😉

As discovered in
googleapis/google-cloud-python#1760, we were
mangling bytes when encoding them as part of a multipart upload request. The
fix is to switch from using `six.StringIO` to `six.BytesIO` in `transfer.py`.
The patch here is closely based on
googleapis/google-cloud-python#1779.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.01%) to 85.672% when pulling 3b42c92 on craigcitro:binary_py3 into d6a3172 on google:master.

@dhermes
Copy link
Contributor

dhermes commented May 9, 2016

Took a look. No glaring issues.

@thobrla
Copy link
Contributor

thobrla commented May 9, 2016

LGTM

@craigcitro craigcitro merged commit 094a7d6 into google:master May 9, 2016
@craigcitro craigcitro deleted the binary_py3 branch May 9, 2016 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants