Date: Sun, 3 Nov 2013 16:07:11 +0100 From: Kurt Jaeger <pi@opsec.eu> To: Jase Thew <jase@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Kurt Jaeger <fbsd-ports@opsec.eu>, William Grzybowski <wg@FreeBSD.org>, ports-committers@freebsd.org Subject: Re: svn commit: r332550 - in head/sysutils/duplicity: . files Message-ID: <20131103150711.GF64348@home.opsec.eu> In-Reply-To: <527660F5.4040901@FreeBSD.org> References: <201311022300.rA2N0snK083676@svn.freebsd.org> <527660F5.4040901@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > Duplicity itself is not fully Python 3 compatible [1] (there's multiple > instances of "print" as command and all the unicode vs bytes string > handling needs resolving to allow woeking unicode filename support), so > simply patching setup.py to prevent a syntax error under Python 3 seems > somewhat bogus. I'm aware of that issue, I just wanted to try to start going python 3. I did not find the time to go further. > There has been work upstream [2] with regards to fully supporting Python > 3 with Duplicity, but this is taking place in a developer branch [3] and > work appears to have stalled. > > Therefore, I think it would be wise to revert this commit and I'll > modify the Makefile to prevent usage with > py27. The change does not really hurt, it just fails later in the install process 8-} -- pi@opsec.eu +49 171 3101372 7 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131103150711.GF64348>