[
https://issues.apache.org/jira/browse/THRIFT-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694653#action_12694653
]
Jonathan Ellis commented on THRIFT-395:
---------------------------------------
> Why is this? We interoperate via Thrift across C++, Ruby, Java, Python2 and
> Erlang here and everything works just fine. We just make limited use of the
> 'string' type - and make sure that applications only send UTF-8 data via
> 'string'.
In other words, you are sending binary data that happens to be an encoded
string and calling _that_ a string, which it is not. It is binary data.
That's working around one bug with another in my book.
> From their perspective, they don't want to "dumb down" their type system
In 2009 a language that doesn't support unicode is barely usable, and will
almost certainly support unicode soon.
AFAIK all the thrift languages do support unicode already but I could be wrong
on one or two.
> 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), Library (Python)
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Blocker
> Fix For: 0.1
>
> Attachments:
> 0001-python-Minor-cleanup-of-protocols-don-t-use-str.patch,
> 0002-THRIFT-395.-python-Phase-One-of-support-for-unicode.patch,
> 0003-THRIFT-395.-python-Phase-Two-of-support-for-unicode.patch,
> 0004-python-Remove-ridiculous-semicolons-from-gen-code.patch,
> python-utf8-v2.patch, 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.
