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
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
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
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, edgar.sol...@web.de wrote:
sounds reasonable.. could you please post some link and/or source comment
these changes
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,
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,
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
base.
New question #219277 on Duplicity:
https://answers.launchpad.net/duplicity/+question/219277
What the magic numbers in the log files?
NOTICE 1
WARNING 1
WARNING 5
INFO 3
I can't found any docs about structure of log files. :-(
Also, what about adding optional support for JSON format of log
New question #219308 on Duplicity:
https://answers.launchpad.net/duplicity/+question/219308
This was a Centos 5.x server that had a catastrophic disk failure. An NFS
export from a Windows Server mounted on /mnt/backup/pbx01 was used to save
backups done through duplicity. All backups were done
9 matches
Mail list logo
