[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] [Duplicity-team] Python 3
From: |
Aaron |
Subject: |
Re: [Duplicity-talk] [Duplicity-team] Python 3 |
Date: |
Thu, 19 Jan 2017 11:39:34 +0000 |
Hi,
On 2017-01-19 10:11, address@hidden wrote:
On 19.01.2017 10:59, Aaron wrote:
Mike Terry already spend some time on python3 support in 0.8, so let's
see if he can comment on the direction he was working in.
Indeed, it would be great to have his input. I'm still early enough on
it that I can change direction. I may have a closer look at Michael
Terry's python 3 branch:
https://code.launchpad.net/~mterry/duplicity/python3
and see how dreadful it would be to bring that up to date (it was based
on a 2015, 0.6-series fork). It would likely save me a lot of work
solving weird corner cases and at the least it will be a useful
reference. I remember Michael describing the status of the branch back
in 2015:
http://lists.nongnu.org/archive/html/duplicity-talk/2015-07/msg00020.html
"it's not in my priority list right now."
well, duplicity is mostly used in shell environments making backups of
servers. these tend to be badly serviced and upgraded (never change a
running sytem), so older software packages stay there and it is a pain
to hand compile newer ones, just for this one usage. i am speaking
from experience here.
so keeping python 2.7 compatibility for some years is afaics a must..
I see that. I guess the question is how long is "some years". Python 3
was released in 2008. Isn't it a bit of a corner case if the machine is
badly serviced and upgraded, but the admin is running a cutting edge
version of duplicity?
Kind regards,
Aaron