Re: [Duplicity-talk] Python 3 or not?

[MRob]

Thank you for kind response Aaron. For long time problems were for the 
age of the duplicity version in CentOS repos. Recently that position 
becames better but ensuing problems became worse when duplicity removed 
in-built support for B2 backend, now B2 must be take from pip3 (iirc) so 
where the version conflicts become terrible. Even so far as library 
installed for pip conflict and break certbot and solution very obscure 
to take couple days googling. Not sure for the detail is important since 
duplicity team maybe make decision b2 is not your responsibility but at 
least in b2 users must beware that 2.7 duplicity is a problem.

Understand its a big job and its free software so cant complain only 
thank you for many years of error free backups.

On 2018-12-04 12:53, Aaron wrote:
> Hello MRob,
> So there are two parts to this: what we are working on and whatever is
> causing your issues.
> As to the plans, as per Mike's email this is in progress :
> https://blueprints.launchpad.net/duplicity/+spec/python3
> I had not yet seen Mike's merge request and thought that was still on
> my todo list, so that is an excellent development. I will try to find
> the time to give that a closer look.
> That said, like Scott I am surprised you are running into issues
> getting this working for you. If you tell us more about your setup
> then we can try to get you up an running.
> I've also been playing with Snap packages, which would include all
> dependencies within the package itself and would solve your dependency
> issues whether we've ported to Python 3 or not. That is looking very
> promising and I have made packages that appear to work, but the work
> is not yet finished.
> Like most decent work items on a volunteer-run project, it is just
> finding the time to progress these larger changes.
> Kind regards,
> Aaron