[
https://issues.apache.org/jira/browse/THRIFT-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729574#action_12729574
]
Terry Jones commented on THRIFT-395:
------------------------------------
> David Reiss writes:
> As I recall, Jonathan was the only person who really seemed to
> care about this issue, and he wasn't satisfied with my
> suggestion, so I put it aside. Chad also requested some changes
> to my diff for the JSON protocol. I'll try to reevaluate the
> status some time soon, but I am away from a computer today.
Jonathan - are you still in the loop on this one? What do you think?
Given the fundamental differences in what a "string" is across different
languages, there's unlikely to be a clean solution that suits everyone. Having
a backwards-compatible compromise that works is much better than having
nothing, though.
> Python library + compiler does not support unicode strings
> ----------------------------------------------------------
>
> Key: THRIFT-395
> URL: https://issues.apache.org/jira/browse/THRIFT-395
> Project: Thrift
> Issue Type: Improvement
> Components: Compiler (Python), Library (Python)
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.2
>
> 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.
