[
https://issues.apache.org/jira/browse/THRIFT-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688328#action_12688328
]
Jonathan Ellis commented on THRIFT-395:
---------------------------------------
> It would break backward compatibility if encoding isn't utf-8.
That's a nonsensical statement. There is no encoding inherent to unicode
objects.
> And there is no way to specify which encoding is used.
That's because read/writeString always use utf-8, so any client can send to any
server.
> The next issue is fastbinary. You'll still get the exception if
> TBinaryProtocolAccelerated is used.
I actually don't know if this bug is present in fastbinary to begin with, but
my understanding is that fastbinary already has some limitations, so if it is,
this can be added to the list. :)
> Python library + compiler does not support unicode strings
> ----------------------------------------------------------
>
> Key: THRIFT-395
> URL: https://issues.apache.org/jira/browse/THRIFT-395
> Project: Thrift
> Issue Type: Bug
> Components: Compiler (Python)
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Blocker
> Attachments: python-utf8.patch
>
>
> Effectively, all strings in the python bindings are treated as binary strings
> -- no encoding/decoding to UTF-8 is done. So if a unicode object is passed
> to a (regular, non-binary) string, an exception is raised.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
