I'm no expert, but I think that line can be dropped. According to the wiki, Thrift supports Python 2.4+. We definitely want to continue supporting the Python 2 family.
I've been thinking a little bit about Python 3 support, and I'm not sure what the best strategy is. I think we should probably start by figuring out what elements of Thrift are deprecated or eliminated in Python 3 before we make any hasty judgments about to proceed. I would definitely like to support both Python 2 and Python 3 simultaneously, so I'm not sure a separate branch is the best approach. The thing that immediately jumps into my mind as far as compatibility is string vs. binary types. For Python 3, I think we should - Add a compiler option that generates binary-aware code. - Make string handling explicitly use utf-8. - Use the byte buffer type for binary fields. --David Dennis Schön wrote: > Hi, > > is there any policy about which python versions are supported? I've > noticed that > the python thrift library issues a warning when used with python 2.6.1: > > /opt/python/lib/python2.6/site-packages/thrift/Thrift.py:44: > DeprecationWarning: BaseException.message has been deprecated as of > Python 2.6 > > It should be pretty trivial to fix that warning but I don't know if we > shouldn't focus > on python 3 support instead. Maybe on a separate branch? > > - Dennis
