[
https://issues.apache.org/jira/browse/THRIFT-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz resolved THRIFT-3500.
------------------------------------------
Resolution: Won't Fix
Python 2 is no longer supported by this project, so this no longer applies to
any shipped runtime.
py2 was removed from the CI workflows in
[e497030b4|https://github.com/apache/thrift/commit/e497030b494b0fbdb662593ac58003a49a26048c]
(2023-06-27); the Six compatibility dependency was dropped in
[8f9fba8a9|https://github.com/apache/thrift/commit/8f9fba8a94b088ea274bd8c544ff997ffee74c9c]
(2024-08-28, released in 0.22.0);
[lib/py/setup.py:139|https://github.com/apache/thrift/blob/master/lib/py/setup.py#L139]
classifies Python 3 only; and the CI matrix in
[.github/workflows/build.yml:652|https://github.com/apache/thrift/blob/master/.github/workflows/build.yml#L652]
tests 3.10 through 3.14.
The str/unicode split this ticket describes does not exist in Python 3, where
{{str}} is text and binary fields are {{bytes}}. Closing as Won't Fix. If a
text/bytes handling problem is still reproducible on Python 3, please open a
new ticket with the failing IDL and payload.
> Protocols in Python 2 do not treat Strings as unicode.
> ------------------------------------------------------
>
> Key: THRIFT-3500
> URL: https://issues.apache.org/jira/browse/THRIFT-3500
> Project: Thrift
> Issue Type: Bug
> Components: Python - Library
> Affects Versions: 0.9.3
> Reporter: John Lockwood
> Priority: Major
>
> Service methods which take a string type param, should expect a unicode
> object in Python 2, but instead expect str.
> Service methods which return string type objects should return a unicode
> object in Python 2, but instead return str.
> When making service calls with Python 2, passing in a unicode object with
> non-ascii chars will raise an exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
