[
https://issues.apache.org/jira/browse/THRIFT-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated THRIFT-395:
----------------------------------
Attachment: python-utf8.patch
This patch adds unicode support to the python bindings. Binary strings
continue to not be encoded/decoded (renamed to readBinary/writeBinary for
consistency w/ other Protocol implementations) and new write/read String
methods were added to support non-binary strings.
There should be no backwards-compatibility problems. `binary` fields will
continue to work as before. `string` fields with ascii data will also continue
to work. The only difference is that you can now pass a unicode object to a
`string` field w/o it breaking.
> 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
> 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.
