Aaron, Backends are the weak part of duplicity testing. We are able to test the backends that have executables but are unable to test backends with web protocols due to need of credentials. Right now we're relying on our users to check the backends and then we make a best effort try at fixing them. Very poor practice, but except for rsync.net, I don't have a relationship with the providers.
...Thanks, ...Ken On Fri, Dec 27, 2019 at 11:21 AM Aaron <[email protected]> wrote: > Hello Kenneth, > > What is the current status of our backend support on Python 3? > > I have seen quite a lot of fixes in the changelog and I see that some of > the Ubuntu folks are finding and patching Python 3 issues, but was > interested in your view of the current status. > > Given the impending EOL of Python 2, it would be nice for us to move to > Python 3 by default. I remember hitting some backend issues with Python > 3 (from memory some of our backends were Python 2 only) when I was > trying to make a Python 3 version of the snapcraft.yaml. It looks like > the snap is still currently based on Python 2. > > At least with snaps we have a bit more control over the transition and > timing, independent of when distros grab their snapshots. > > Kind regards, > > Aaron > >
_______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
