This repository was archived by the owner on Aug 7, 2024. It is now read-only.
Fixed Non-ASCII printable representation in Trend - #249
Merged
Conversation
When __repr__ is called on a Trend object, non-ASCII character leads to a UnicodeEncodeError.
Owner
|
thanks! |
bear
added a commit
that referenced
this pull request
Oct 11, 2015
Fixed Non-ASCII printable representation in Trend
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi,
When
__repr__is called on a Trend object, non-ASCII character leads to a UnicodeEncodeError.When did this bug occur?
I am a German twitter User. The API broke on a Trend with name 'Dinge die Mädchen'. The ä is a non-ASCII character. The full error code was:
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 11: ordinal not in range(128)I am not sure, if this may occur in other method calls. Basically, Non-ASCII characters should be supported, since twitter is used world-wide.
Thanks for the great API.
Cheers
Daniel