From owner-svn-ports-all@FreeBSD.ORG  Sun Nov  3 15:07:18 2013
Return-Path: <owner-svn-ports-all@FreeBSD.ORG>
Delivered-To: svn-ports-all@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 4DD74C24;
 Sun,  3 Nov 2013 15:07:18 +0000 (UTC) (envelope-from pi@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 03D1322DC;
 Sun,  3 Nov 2013 15:07:17 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD))
 (envelope-from <pi@opsec.eu>)
 id 1VczGh-000D1p-Fp; Sun, 03 Nov 2013 16:07:11 +0100
Date: Sun, 3 Nov 2013 16:07:11 +0100
From: Kurt Jaeger <pi@opsec.eu>
To: Jase Thew <jase@FreeBSD.org>
Subject: Re: svn commit: r332550 - in head/sysutils/duplicity: . files
Message-ID: <20131103150711.GF64348@home.opsec.eu>
References: <201311022300.rA2N0snK083676@svn.freebsd.org>
 <527660F5.4040901@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <527660F5.4040901@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
X-BeenThere: svn-ports-all@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: SVN commit messages for the ports tree <svn-ports-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-ports-all>,
 <mailto:svn-ports-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-ports-all>
List-Post: <mailto:svn-ports-all@freebsd.org>
List-Help: <mailto:svn-ports-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-ports-all>,
 <mailto:svn-ports-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Nov 2013 15:07:18 -0000

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 !