[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Backend API support
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Backend API support |
Date: |
Mon, 23 May 2016 10:43:36 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 |
On 23.05.2016 08:38, Scott McKenzie via Duplicity-talk wrote:
> Hi list
>
> I'm looking for some advice on which versions or how many versions of an API
> a backend should reasonably support. The Azure backend uses the Microsoft
> Azure Storage SDK for Python (https://github.com/Azure/azure-storage-python)
> which is under active development. This means that API objects and methods
> are a moving target. I'm currently updating it to support the latest version
> and it's looking a bit "messy". There are a few hasattr() calls to determine
> which objects to instantiate and which methods to call on those objects.
>
> Does the duplicity project have any guidelines for this? If so, please point
> me towards them.
nope
> If not, how many versions do you think a backend should support? Should the
> supported/required versions be documented in the duplicity man page?
my take would be:
1. use a version/versions that is/are reasonably stable, that you use/tested
2. communicate the version(s) that the backend works w/ in the manpage
3. maybe add download locations if they are "hidden" for older versions
..ede/duply.net