-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Various improvements re character encoding and testing #11
Open
asmundg
wants to merge
10
commits into
jtushman:master
Choose a base branch
from
asmundg:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
As a side-effect, this makes us use unicode, which will be useful for non-ascii characters in aythor and story names down the line.
Just to prove that my initial changes work.
Python doesn't let us know the terminal encoding if we're piping (which may or may not be correct, depending on who you ask). So we need some extra handling. Incidentally, handling the output differently also makes is easier to test that we're getting the right output. I've only implemented this for show_stories thus far.
Fetching and displaying information are two distinct tasks, one of which is functional.
Also basic testing and separation of concerns.
Seeing these is useful in some workflows,
I've tested here and the story title stills bad. I received the unicode error on |
yay -- pull request -- I will review shortly |
(and sorry I did not see this earlier) |
Apparently, ElementTree likes to do it's own decoding. It raises a UnicodeError when given the decoded response.text, but it works fine when given the raw response.content.
Use the binary response content instead of unicode
So I know that this pull hasn't been merged or accepted yet but I just downloaded the fork and it makes something that doesn't work, work! You should probably merge this 😄 👍 |
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.
These are mostly improvements I needed myself, but they're relevant for #7, #9 and #10.