Open
Conversation
FIX: string access on byte sequence and type cast for invocation of mail message function
Owner
|
Thanks @nnako for your work! However, I don't think the key itself should be bytes, should it? According to the py33 test in travis, the key doesn't exist. The py27 test needs fixing, because it's mocked. If you need help fixing those two test failures, please let me know. |
|
+1 on this pull: from the IMAPClient documentation, in Python 3 it returns messages as byte arrays, instead of strings as in Python 2. The patch is needed to have it working on Python 3. |
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
3 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.
FIX: string access on byte sequence and type cast for invocation of mail message function