[ 
https://issues.apache.org/jira/browse/THRIFT-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528333#comment-13528333
 ] 

Todd Lipcon commented on THRIFT-1773:
-------------------------------------

Jake and I caught up on IRC last week to discuss this. I think through sheer 
stubbornness I convinced him that we should continue to support Python 2.4 for 
the foreseeable future.

The summary of the points are:
- It's not possible to write code which is both compatible with Python 2.4 and 
Python 3.0, due to this incompatible change described in PEP 3110. Code that is 
compatible with Python 2.4 is also compatible with the latest Python 2.x.
- CentOS (and RHEL) 5.x only ship Python 2.4.
- There are no distros which _only_ ship Python 3.0 -- all the distros with 3.0 
continue to offer 2.7.x as well.

So, the choice that supports the widest set of distros is to continue to code 
against 2.4 and not support 3.0. If at some point we really need some feature 
which is only available in 3.x, we could re-evaluate, but given that many 
people seem to ship software which has to run on RHEL5, there's not sufficient 
motivation yet.

Jake -- let me know if I got any of the above wrong. If you agree with the 
above, then we should revert THRIFT-1604, which should be sufficient to restore 
2.4 compatibility.
                
> Python library should run on python 2.4
> ---------------------------------------
>
>                 Key: THRIFT-1773
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1773
>             Project: Thrift
>          Issue Type: Bug
>          Components: Python - Library
>    Affects Versions: 0.9
>            Reporter: Todd Lipcon
>            Assignee: Jake Farrell
>
> As of 0.9, the Python code seems to require Python >= 2.6 (eg using new 
> syntax not available in 2.4). Since many people still run Thrift-based apps 
> on RHEL5, which includes only 2.4, we should avoid this dependency.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to