tools/sched: Fix unicode encoding issues #2220
Closed
Conversation
This file contains 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
The response.text and json-parsed string values are both unicode strings. The print statement requires bytes, as per write(2). Python is dumb and bad at converting between them properly - in the name of being "safe" it errors if any non-ascii characters are present, so it works until it doesn't. We fix this by explicitly encoding as utf-8.
|
|
|
ah, dammit. the name caught me out.
…On 8 Feb. 2017 6:01 pm, "Alfonso Acosta" ***@***.***> wrote:
tools is a subtree of https://github.com/weaveworks/build-tools , please
fix is there instead
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2220 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAiyxB1lEQuajDq7SiEQEOwaXaUY92Qcks5ranOBgaJpZM4L7m66>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The response.text and json-parsed string values are both unicode strings.
The print statement requires bytes, as per write(2).
Python is dumb and bad at converting between them properly - in the name of being "safe"
it errors if any non-ascii characters are present, so it works until it doesn't.
We fix this by explicitly encoding as utf-8.