you once tried to maintain a second branch "0.7" .. i don't think this is a way
to go considering man power vs. doubled maintenance effort.
i agree with Michael on the "we have to try" attitude. the setup approach
allows to start with the adaption while still keeping our stable python2 code
bas
Separate repositories seems like a non-starter to me. Since we aren't
ready to drop 2.4, I think converting on the fly is a reasonable offering
until we are. We don't have to officially support it, but I think it's a
workable step on the path to Python 3 support.
-mt
On 15 January 2013 10:31, K
With setup.py almost anything is possible, but I would be suspicious of
converting 2to3 on the fly. I think it would have to be a separate code
base and separate repositories. One code base could be possible once we
drop versions below 2.6.
...Ken
On Tue, Jan 15, 2013 at 4:05 AM, wrote:
> how
https://wiki.ubuntu.com/Python/3 is a great resource, both for the tips it
includes directly and the list of further reading at the bottom.
-mt
On 15 January 2013 08:58, wrote:
> sounds reasonable.. could you please post some link and/or source comment
> these changes extensively so it'd be eas
sounds reasonable.. could you please post some link and/or source comment these
changes extensively so it'd be easier for other devs to reuse, add to your
changes?
..ede
On 15.01.2013 14:51, Michael Terry wrote:
> The distribute package has some support for doing this cleanly. You can put
> t
The distribute package has some support for doing this cleanly. You can
put the following in your setup.py:
extra = {}if sys.version_info >= (3, 0):
extra.update(
use_2to3=True,
use_2to3_fixers=['custom_fixers']
)
And put custom 2to3 code that the tool didn't fix automat
how would you figure this? patching during setup? install different file
versions? sounds messy.
..ede
On 15.01.2013 03:29, Michael Terry wrote:
> Hrm. OK. I wonder if we can't offer an option to 2to3 on the fly during
> setup.py if the user wants to install for python3.
> -mt
>
>
> On 14 J
Hrm. OK. I wonder if we can't offer an option to 2to3 on the fly during
setup.py if the user wants to install for python3.
-mt
On 14 January 2013 12:32, wrote:
> as we don't really have hurry with that decision i vote for keeping an eye
> out how stable the next 0.6 release works out, and rec
as we don't really have hurry with that decision i vote for keeping an eye out
how stable the next 0.6 release works out, and reconsidering a move to a
python2.6+ duplicity 0.7 again thereafter.
..ede
On 14.01.2013 15:44, Michael Terry wrote:
> My personal push for Python 3 support is because
My personal push for Python 3 support is because Ubuntu is pushing to be
able to ship only Python 3 on the desktop image. (Plus, Python 2.7 is the
last Python 2.x. We're at the end of that life line.)
In that context, dropping support for Python 2.4 is important because it is
vastly simpler to w
i'd limit it to data critical fixes. we simply have no man power to maintain
both series. on the other hand, what exactly is pressing us to python3 or even
python2.6..
isn't it merely keeping an eye out not to hack something backwards incompatible?
if so, we could simply announce that we do not
I think we have to continue support of the 0.6 series for a while, open to
discussion.
As to 0.7, good idea. New features can be added here, fixes go to both
series.
...Ken
On Sun, Jan 13, 2013 at 5:54 AM, wrote:
> On 13.01.2013 02:25, Michael Terry wrote:
> > Hello! Yet another thread on th
On 13.01.2013 02:25, Michael Terry wrote:
> Hello! Yet another thread on the slow march to Python 3 support.
>
> The last place we left it was that Ubuntu was considering throwing some
> effort behind porting duplicity and maintaining such a patch themselves.
> That didn't happen for manpower
Hello! Yet another thread on the slow march to Python 3 support.
The last place we left it was that Ubuntu was considering throwing some
effort behind porting duplicity and maintaining such a patch themselves.
That didn't happen for manpower reasons.
But I notice that Red Hat just passed (Jan 8,
14 matches
Mail list logo
