Address unicode failures by using requests response.content#23
Merged
graysonarts merged 1 commit intomasterfrom Sep 8, 2016
Merged
Address unicode failures by using requests response.content#23graysonarts merged 1 commit intomasterfrom
graysonarts merged 1 commit intomasterfrom
Conversation
…an text so things are encoded properly when passed to element tree
Collaborator
|
Reminds me of t8y8/rickbot@2462df6 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ElementTree can handle encoded unicode, so we use response.content rather than response.text which tries to decode the unicode.