Hello! I was reading a colleague's post about porting packages to Python 3 [1] and it made me think of duplicity.
The basic gist is that an easy way to port is to have the same codebase for 2.6+ and 3.2+ by clever use of future imports and some caution. No 2to3.py necessary. For the next, oh, year or so, I expect we will want to keep 2.4 support. But in 2013, we could maybe bump the minimum RHEL supported (I assume? -- I think that roughly tracks to the point in the previous RHEL lifecycle when we bumped up to 2.4). That would jump us to 2.6 as the minimum Python. And then we could support 3.2 relatively easily (it seems). I don't have time to work on a branch right now (and it wouldn't even be able to be merged until closer to 2013 anyway), but I feel like that would be the way to go when we are ready. Thoughts? -mt [1] http://www.wefearchange.org/2012/01/python-3-porting-fun-redux.html _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
