Handling unicode arguments #175
Merged
Conversation
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
|
Thank you very much - I am merging this one in to make the fix available right away. When git-python at some point becomes compatible to Py3, these kinds of issues would hopefully be handled naturally. After all, all strings with text would be unicode then. |
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.
There is an issue with the handling of unicode arguments. This situation occurs when you have file named with unicode characters, that is returned correctly from GitPython as a Unicode type, if you then try and feed that back into the API it's not handled when unpacking the arguments.
I'm not sure how to make the repository encoding available at this point, so our fix currently just uses the default and we haven't run into anyone not using a repository with the default encoding.