Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
upload
example Python 3 friendly.tuspy
back to0.2.1
as an exact match.Why:
tuspy
library changes will not function with Python 2.7 out of the box, without modifications.Tidbits:
tuspy
versions>=0.2.2
.tuspy
version0.2.1
.The difference between them, is the
TusRequest.handle
attribute. For0.2.1
it is apycurl
instance, which appears to be able to handle unicode characters in a Python2.7
string.While the
TusRequest.handle
attribute for versions>=0.2.2
is anhttp.client.HTTPSConnection
instance which appears to not function for Python2.X
, even if at the IO boundary we specify the file encoding asutf-8
.The screenshot below, demonstrates an upload (which was failing in the same manor as various user reports) is now succeeding.
TL;DR This should fix the various user reports that have been received.
@erunion
// #134 #135