[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Python 3 or not?
From: |
Mike Gorse |
Subject: |
Re: [Duplicity-talk] Python 3 or not? |
Date: |
Mon, 3 Dec 2018 09:53:54 -0600 (CST) |
User-agent: |
Alpine 2.21 (LSU 202 2017-01-01) |
There is a Launchpad blueprint for it, and people have attempted to do a
port. I suspect that it isn't done yet due to lack of time and it being
non-trivial (mostly because of string vs. bytes changes in python 3).
https://blueprints.launchpad.net/duplicity/+spec/adorn-string-literals
I've been trying to work on porting the code, since SUSE will likely need
to have it ported. I submitted a merge request last week for a first pass,
but it is a very large patch that someone would need to look over.
On Fri, 30 Nov 2018, MRob via Duplicity-talk wrote:
Hi, I keep running into deployment headaches based on conflicts with python 3
versoin of pip and other libaray problems. It feels like a big mess and many
hoops jumped through downgrading packages or hand compiling obscure libaraies
I should not have to touch.
Been many happy years with duplicity so i thank you but are you not planning
to support modern software stack? If not, someone here might have kind advice
on a quality replacement as reliable as duplicity and support so many
features?
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk