Re: [Duplicity-talk] Python 3

[Michael Terry]

It is possible to have a single source be both compatible, if you use
a script to generate both.  Like you can have the original source be
either 2 or 3 and use a script like py2to3 or py3to2 to make the
other.  This requires a bit of care I believe and would probably mean
having original source be at least 2.6 and up instead of 2.4 and up.

I think such scripts are considered a stopgap measure and the Python
people (obviously) prefer you to be on Python 3 only.  But generating
both versions is a viable option.

-mt

On 9 April 2011 09:31, Kenneth Loafman <address@hidden> wrote:
> I've not looked at Python 3.  Only one question comes to mind that may be a
> serious impediment -- Is it possible to have a single source that is 2.x and
> 3.x compatible, or is this going to be a major rewrite?
>
> ...Ken
>
> On Sat, Apr 9, 2011 at 7:59 AM, Michael Terry <address@hidden> wrote:
>>
>> Hello!  I wanted to start a conversation about moving to Python 3.  I
>> know this is far in the future likely, but it might be interesting to
>> plan around it.
>>
>> Currently duplicity only requires Python 2.4, which is 4 years older
>> than Python 3.0.  3.0 is about as old as 2.6, so maybe it would make
>> sense that when we are considering a jump to Python 2.6, we might as
>> well also consider Python 3?
>>
>> Of course there are dependencies to wait on as well.  And the work has
>> to be done by someone.
>>
>> It doesn't need to be all-at-once either, I believe.  We could update
>> to 2.6 or 2.7 and use a program like py2to3 to generate the 3.0 code
>> until we're comfortable making the full jump?
>>
>> -mt
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>