duplicity-team team mailing list archive

[Michael Terry <mike@xxxxxxxxxxx>]

On 20 November 2013 14:49, Kenneth Loafman <kenneth@xxxxxxxxxxx> wrote:

> At one time 0.7 was slated for PAR inclusion.  There was a partial
> development on it, but it's seen no activity in a couple of years.
>

I was thinking of not bothering trying to resurrect the old 0.7 branch and
more along the lines of just forking current trunk into a 0.6 maintenance
branch and continue working in trunk.


It's time to go to either 0.7 or 1.0.  If we've really fixed the data
> corruption bugs, then maybe 1.0.
>

Eh, we can't ever know.  Either number is fine for me.  I just don't like
so many digits in my versions.  :)  deja-dup is up to 23.1 now.



>  Python wouldn't introduce new features like that in a point release.
>> 'unicode_literals' and 'print_function' were both introduced in 2.6.
>> That's the main reason to want the bump.
>>
>
> I thought one of the problems was librsync not having a presence on 3.x.
>  There may be others missing.
>

I believe everything needed for basic functionality is available in
python3.  The bits I remember missing are some of the backend imports.  But
requiring 2.6 will let us get the main code base "bilingual" ready at
least.  Backends can be ported one at a time, as their imports allow.

-mt