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

ASF GitHub Bot commented on THRIFT-3515:
----------------------------------------

GitHub user nsuke opened a pull request:

    https://github.com/apache/thrift/pull/766

    THRIFT-3515 Python 2.6 compatibility and test on CI

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nsuke/thrift THRIFT-3515

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/thrift/pull/766.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #766
    
----
commit 76903f43abc9341bc60688a27e063928354812cb
Author: Nobuaki Sukegawa <[email protected]>
Date:   2016-01-03T05:24:39Z

    THRIFT-3515 Python 2.6 compatibility and test on CI

----


> Python 2.6 compatibility and test on CI
> ---------------------------------------
>
>                 Key: THRIFT-3515
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3515
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Python - Library
>            Reporter: Aki Sukegawa
>            Assignee: Aki Sukegawa
>            Priority: Minor
>
> There were a few trivial problems with Python 2.6.
> * format string '{}' is not supported
> * bytearray cannot be used as str
> While we can drop 2.6 support now, IMO there isn't enough motivation yet.
> With 2.7.9 enhancement for SSL, it makes sense to me to drop 2.7.8- once 
> major distros have 2.7.9+. (jessie has 2.7.9 but trusty still has 2.7.6 amd 
> CentOS 7, 2.7.5)
> With the patch, it should be now fully compatible with 2.6.
> I also added Travis build that runs python test with Python 2.6 on CentOS 6.
> For some reason I had to adjust CMake script to successfully configure 
> without C++ and C-GLib.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to